When deployed under Tomcat, Jenkins requires to have this option set :
This is a known issue/limitation/prerequisite like described in:
The reverse proxy monitor was verifying this originally ( info confirmed by Jesse Glick ) :
But it was lost in this commit: https://github.com/jenkinsci/jenkins/commit/cffe9df0176b0ff895554ce7f2ea4d2f20062351 (1.572)
I'm not sure that all these controls should be in the same monitor but for sure the test must be done.
- to be re-added in the reverse proxy monitor to verify when the problem comes from the reverse proxy.
- to be re- added as a specific Monitor for Tomcat because if org.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH isn't set it will break some Jenkins features (400 HTTP Error - Bad Request with AJAX calls inside Folders for example, ...) even if there is no reverse proxy configured.
|Labels||diagnostics reverse-proxy tomcat|
|Labels||diagnostics reverse-proxy tomcat||diagnostics regression reverse-proxy tomcat|
|Workflow||JNJira [ 166236 ]||JNJira + In-Review [ 182319 ]|
|Labels||diagnostics regression reverse-proxy tomcat||diagnostics newbie-friendly regression reverse-proxy tomcat|
|Assignee||Josiah Haswell [ jhaswell ]|
|Status||Open [ 1 ]||In Progress [ 3 ]|
|Status||In Progress [ 3 ]||In Review [ 10005 ]|
|Remote Link||This issue links to "jenkins#2977 (Web Link)" [ 17530 ]|
|Status||In Review [ 10005 ]||Resolved [ 5 ]|
|Resolution||Fixed [ 1 ]|
|Remote Link||This issue links to "CloudBees Internal OSS-308 (Web Link)" [ 18918 ]|