That's why the curl command specifies a referer, something you don't have if 
you just open that URL.

On 12.03.2015, at 09:16, Marcos Rey <[email protected]> wrote:

> If it helps, if i manually try the url: https://hostname/jenkins/manage 
> https://hostname/jenkins/administrativeMonitor/hudson.diagnosis.ReverseProxySetupMonitor/test,
>  tomcat returns this:
> 
> HTTP 404 - https://hostname/jenkins/manage vs. NO-REFERER
> 
> El jueves, 12 de marzo de 2015, 9:14:49 (UTC+1), Marcos Rey escribió:
> Thanks Rui, i would consider mod_ajp. The weird thing is that i have a 
> similar production deployment that does not have this issue.
> 
> Mark, thanks for sharing your config, mine is quite similar, but I still get 
> the proxy reverse broken error. The weird thing is that everything seems to 
> be working fine, so I might skip this for the meanwhile. Also, could you 
> please verify that your installation passes the 'curl' test?
> 
> curl -iL -e https://hostname/jenkins/manage 
> https://hostname/jenkins/administrativeMonitor/hudson.diagnosis.ReverseProxySetupMonitor/test
> 
> Also, I'm using https... I'm not sure if that's what's causing the issue.
> 
> Thanks both for your help and for taking your time to answer.
> 
> El jueves, 12 de marzo de 2015, 0:54:57 (UTC+1), Mark Eggers escribió:
> I've not seen this.
> 
> For my Jenkins URL:
> 
> http://[hostname]/jenkins/
> 
> In my uriworker.properties file:
> 
> /jenkins|/*=[workername]
> 
> Then in the Apache HTTPD host that manages Jenkins:
> 
> JkMountFile conf.d/uriworkermap.properties
> 
> There's a good base workers.properties configuration example in conf 
> subdirectory of the mod_jk source code.
> 
> I'm running 1.602 on CentOS 6.6, Apache HTTPD 2.2.15-39, mo_jk 1.40, Tomcat 
> 7.0.57, and Oracle JRE 1.7.0_76 64 bit. I'm using the APR connector (Tomcat 
> native compiled and in Java library path). All my connectors are set to UTF-8.
> 
> . . . just my two cents
> /mde/
> 
> On Wednesday, March 11, 2015 at 2:25:13 PM UTC-7, Rui Fernando Hayashi wrote:
> I've managed to solve that using mod_proxy_ajp.
> 
> On Wed, Mar 11, 2015 at 7:37 AM, Marcos Rey <[email protected]> wrote:
> Hello!
> 
> I've been reading the messages around the list and I see that more people see 
> this message on 'Manage Jenkins' when running apache+mod_jk with Jenkins. Any 
> input would be greatly appreciated.
> 
> Regards,
> 
> 
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/c66b22b3-b92b-440b-be5c-97be4e2e2d40%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/ce205e87-be25-4b28-b033-8c70268e0ecb%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/DABF83D0-9FEB-46D1-93A5-FBA5E26C2F05%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Reply via email to