-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jenkins URL #248
Comments
There's been some debate over this over the years, Why can't you access it over the configured Jenkins url? |
For example we use separate port for HTTP2. Also some of users prefer to use just IP address, some use DNS. |
Why can't you access it over 1 port using http/2 for everything? I would accept a pull request making it configurable as either an advanced option or a system property. |
Because HTTP2 is not supported everywhere. Still we want to test it. Can we turn around the question - why can't we just use relative links and make everyone happy?
|
Because people run Jenkins on different context paths, you aren't able to use |
Jenkins and plugins versions report
Theme Manager plugin add JENKINS_URL to css files. When user access Jenkins by different address than that configured as JENKINS_URL, the browser blocks some files because of:
"A cross-origin resource sharing (CORS) request was blocked because of invalid or missing response headers of the request or the associated preflight request ."
I believe links to css should be relative.
Reported also as https://issues.jenkins.io/browse/JENKINS-72816
What Operating System are you using (both controller, and any agents involved in the problem)?
Linux, official docker images for jenkins
Reproduction steps
Access jenkins by URL different that configured as JENKINS_URL
Expected Results
relative links to css files
Actual Results
blocked by browser when accessing via different url than JENKINS_URL or different port. For example we use separate port for HTTP2
Anything else?
No response
Are you interested in contributing a fix?
No response
The text was updated successfully, but these errors were encountered: