Thanks for your reply, Stephen.
Here's the IIS web.config file. Does anyone know how the rewrite rule
should be configured for Jenkins?
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<system.webServer>
<security>
<requestFiltering allowDoubleEscaping="true" />
</security>
<rewrite>
<rules>
<rule name="ReverseProxyInboundRule1" stopProcessing="true">
<match url="(.*)" />
<action type="Rewrite" url="http://localhost:8080/{R:1}";
/>
<serverVariables>
<set name="HTTP_X_FORWARDED_HOST" value=
"{HTTP_HOST}" />
<set name="HTTP_X_FORWARDED_SCHEMA" value="https" />
<set name="HTTP_X_FORWARDED_PROTO" value="https" />
</serverVariables>
</rule>
</rules>
</rewrite>
</system.webServer>
</configuration>
?
Thanks,
Terry
On Thursday, May 25, 2017 at 4:41:36 PM UTC-6, Stephen Connolly wrote:
>
>
> https://our.server.name/administrativeMonitor/hudson.diagnosis.ReverseProxySetupMonitor/testForReverseProxySetup/https%3A%2F%2Four.server.name%2Fmanage/
>
> Looks like the URL rewrite rule is setup wrong and is double prefix with
> https://...
> On Thu 25 May 2017 at 20:45, Terry Lacy <terry...@gmail.com <javascript:>>
> wrote:
>
>> Here's some extra information I haven't posted before.
>>
>> The wiki page linked from the "More Info" button (
>> https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+says+my+reverse+proxy+setup+is+broken)
>>
>> says this curl command will provide more info:
>>
>> curl -iL -e http://your.reverse.proxy/jenkins/manage \
>> http:
>> //your.reverse.proxy/jenkins/administrativeMonitor/hudson.diagnosis.ReverseProxySetupMonitor/test
>>
>> I ran that from one of our linux servers. This was the result:
>>
>> $ curl -u 'XXXX:XXXXXXXX' -iL -e https://our.server.name/manage
>> https://our.server.name/administrativeMonitor/hudson.diagnosis.ReverseProxySetupMonitor/test
>>
>>
>> HTTP/1.1 302
>> Cache-Control: private
>> Content-Length: 0
>> Expires: Wed, 31 Dec 1969 17:00:00 MST
>> Location: https://
>> our.server.name/administrativeMonitor/hudson.diagnosis.ReverseProxySetupMonitor/testForReverseProxySetup/https%3A%2F%2Four.server.name%2Fmanage/
>> X-Content-Type-Options: nosniff
>> X-Powered-By: ARR/3.0
>> Date: Thu, 25 May 2017 19:30:37 GMT
>>
>>
>> HTTP/1.1 404
>> Cache-Control: private
>> Content-Length: 1116
>> Content-Type: text/html;charset=utf-8
>> Content-Language: en
>> Expires: Wed, 31 Dec 1969 17:00:00 MST
>> X-Content-Type-Options: nosniff
>> X-Powered-By: ARR/3.0
>> Date: Thu, 25 May 2017 19:30:40 GMT
>>
>>
>> <!doctype html><html lang="en"><head><title>HTTP Status 404 – Not
>> Found</title><style
>> type="text/css">h1
>> {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;}
>>
>> h2
>> {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;}
>>
>> h3
>> {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;}
>>
>> body
>> {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} b
>> {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;}
>> p
>> {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}
>>
>> a {color:black;} a.name {color:black;} .line
>> {height:1px;background-color:#525D76;border:none;}</style></head><body><h1>HTTP
>>
>> Status 404 – Not Found</h1><hr class="line" /><p><b>Type</b> Status
>> Report</p><p><b>Message</b> https://our.server.name/manage vs.
>> https:</p><p><b>Description</b> The origin server did not find a current
>> representation for the target resource or is not willing to disclose that
>> one exists.</p><hr class="line" /><h3>Apache
>> Tomcat/8.5.14</h3></body></html>
>>
>> Any helpful information there?
>>
>> Terry
>>
>>
>> On Wednesday, May 24, 2017 at 9:51:29 AM UTC-6, Terry Lacy wrote:
>>>
>>> I posted a bug (https://issues.jenkins-ci.org/browse/JENKINS-44239
>>> <https://www.google.com/url?q=https%3A%2F%2Fissues.jenkins-ci.org%2Fbrowse%2FJENKINS-44239&sa=D&sntz=1&usg=AFQjCNFOzIKQy7-TB-JzmTLJv3hrUkkNhg>),
>>>
>>> and it was resolved as "not a defect", so I'm back here, still looking for
>>> a solution.
>>>
>>> Does anyone here run Jenkins behind IIS? Are you using a recent version?
>>> Are you able to get rid of the "It appears that your reverse proxy set up
>>> is broken" error?
>>>
>>> Thanks,
>>> Terry
>>>
>>
>>
>> --
>> 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 jenkinsci-use...@googlegroups.com <javascript:>.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/e9d7f7ee-2494-40a9-b0af-1f8ee57ec037%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/jenkinsci-users/e9d7f7ee-2494-40a9-b0af-1f8ee57ec037%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> Sent from my phone
>
--
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/81c09450-8a1c-410a-b79f-ce2f1f5b013b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
