-
Bug
-
Resolution: Fixed
-
Major
Under some conditions a reverse proxy may define X-Forwarded-Port yet the Jenkins servlet container still returns 80 for ServletRequest.getServerPort. This causes problems for computing Jenkins.getRootUrlFromRequest, the current implementation of which treats the default port as 80 regardless of the scheme; we would like the default to be 443 when X-Forwarded-Proto: https, yet this will only work if the servlet container coƶperates. Easier to have Jenkins itself interpret this header when set.
- depends on
-
JENKINS-31068 The reverse proxy monitor doesn't verify anymore if org.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH=true on Tomcat
-
- Resolved
-
- is related to
-
JENKINS-10675 Jenkins redirecting from https to http
-
- Resolved
-
Code changed in jenkins
User: Stephen Connolly
Path:
core/src/main/java/jenkins/model/Jenkins.java
http://jenkins-ci.org/commit/jenkins/5bad446dd51d31efd60538eab5c87bdde57114e9
Log:
[FIXED JENKINS-23294] Interpret X-Forwarded-Port
that a header value may contain a comma separated list if there were multiple forwarding hops.