On Tue, Mar 25, 2014 at 03:46:41PM -0700, Dennis Jacobfeuerborn wrote: > Never mind. It looks like this is actually a bug in Jenkins: > > https://issues.jenkins-ci.org/browse/JENKINS-21989
That's not a bug. If I set up Apache properly[1], I get a 200 Ok from the curl test. [1] https://issues.jenkins-ci.org/browse/JENKINS-21989?focusedCommentId=197468&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-197468 > On Thursday, March 20, 2014 5:05:47 PM UTC+1, Dennis Jacobfeuerborn wrote: > > I just installed a fresh Jenkins behind Apache httpd and while Jenkins is > > available it tells me "It appears that your reverse proxy set up is > > broken." but I don't know why. > > > > This is my httpd config: > > > > <VirtualHost *:80> > > ServerName jenkins.local > > ProxyRequests Off > > ProxyPreserveHost On > > ProxyPass / http://127.0.0.1:8080/ > > ProxyPassReverse / http://127.0.0.1:8080/ > > </VirtualHost> > > > > What specifically is wrong with this configuration? You need 'AllowEncodedSlashes NoDecode' and you need to append 'nocanon' to the 'ProxyPass /' line: <VirtualHost *:80> ServerName jenkins.local ProxyRequests Off ProxyPreserveHost On ProxyPass / http://127.0.0.1:8080/ nocanon ProxyPassReverse / http://127.0.0.1:8080/ AllowEncodedSlashes NoDecode </VirtualHost> (I didn't know about this curl test and these requirements before this thread, and so my configuration I pasted upthread didn't show them. I'm somewhat curious why my Jenkins never complained about improper proxy setup. Maybe I just dismissed that warning.) Marius Gedminas -- <niemeyer> I'm wondering why we have defineChecker() defined twice with exactly the same implementation under zope.security.checker... <niemeyer> Is it some kind of high-availability system? :-) -- #zope3-dev
signature.asc
Description: Digital signature
