I get the 404, but I don't get any errors on the management pages.

I don't think that referring to mod_jk as a proxy is strictly correct. See 
the following for a detailed explanation.

http://tomcat.apache.org/connectors-doc/generic_howto/proxy.html

As an aside - mod_proxy_ajp is basically mod_jk. It's just that the 
configuration is different (both use AJP/1.3 under the covers).

You may run into some problems if you're serving Jenkins from differing 
contexts. For example:

1. Web server - http://hostname/ --> gets to Jenkins
2. Tomcat     - http://hostname:8080/jenkins/ --> gets to Jenkins

In those cases you'll probably have to do some rewriting.

I haven't done extensive Jenkins programming, so I don't know if my setup 
breaks for any of the use cases mentioned here:

https://wiki.jenkins-ci.org/display/JENKINS/Hyperlinks+in+HTML

I've also not trolled through all the pages to see if the Location header 
is being rewritten properly (no port 8080). However, I suspect that it is 
since the site works.

The only issue I'm observing is that pages representing modules in 
multi-module builds aren't being rendered correctly in Chrome. Much of the 
formatting and hyperlinks are missing. However, the same pages render 
correctly in Firefox. I suspect it's a Chrome vs. Jenkins issue.

. . . . just my two cents
/mde/


On Thursday, March 12, 2015 at 2:00:28 AM UTC-7, Marcos Rey wrote:
>
>
> Forgot to append the output:
>
> HTTP/1.1 302 Found
> Date: Thu, 12 Mar 2015 08:57:51 GMT
> Server: Apache/2.2.15 (CentOS)
> Cache-Control: private
> Expires: Thu, 01 Jan 1970 01:00:00 CET
> Location: 
> https://hostname/jenkins/administrativeMonitor/hudson.diagnosis.ReverseProxySetupMonitor/testForReverseProxySetup/https%3A%2F%2Fhostname%2Fjenkins%2Fmanage/
> Content-Length: 0
> Connection: close
> Content-Type: text/plain; charset=UTF-8
>
> HTTP/1.1 404 Not Found
> Date: Thu, 12 Mar 2015 08:57:52 GMT
> Server: Apache/2.2.15 (CentOS)
> Content-Length: 442
> Connection: close
> Content-Type: text/html; charset=iso-8859-1
>
> <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
> <html><head>
> <title>404 Not Found</title>
> </head><body>
> <h1>Not Found</h1>
> <p>The requested URL 
> /jenkins/administrativeMonitor/hudson.diagnosis.ReverseProxySetupMonitor/testForReverseProxySetup/
> https://hostname/jenkins/manage/ was not found on this server.</p>
> <hr>
> <address>Apache/2.2.15 (CentOS) Server at hostname Port 443</address>
> </body></html>
>
>
>
> El jueves, 12 de marzo de 2015, 9:55:59 (UTC+1), Marcos Rey escribió:
>>
>>
>> You are totally right, my bad. If I try the curl test, I get a 404 (as 
>> expected).
>>
>> El jueves, 12 de marzo de 2015, 9:47:08 (UTC+1), Daniel Beck escribió:
>>>
>>> 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/2958fdd1-709a-4594-ad07-49f09fde2656%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to