Yep, that's covered, but still not making progress
El viernes, 13 de marzo de 2015, 11:38:44 (UTC+1), Daniel Beck escribió:
>
>
> On 13.03.2015, at 10:34, Marcos Rey >
> wrote:
>
> > The only difference is that apache also servers in port 80 while in the
> new
gt; 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 Fou
: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
; On 12.03.2015, at 09:16, Marcos Rey >
> 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:
> >
> &
), 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.
TF-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 wrote:
>>
>>&g
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
"Jenk
