There is still a case not working properly though...
Suppose the following setup:

  • Apache Front end with SSL exposing Jenkins with the following URL: https://jenkins.mydomain.com
  • Apache mod_proxy is configured to forward requests to Jenkins at http://localhost:3005 as follows:
    ProxyRequests     Off
      ProxyPreserveHost On
    
      <Location />
        ProxyPass        http://localhost:3005/
        ProxyPassReverse http://localhost:3005/
      </Location>





In this case, Jenkins still compains saying my reverse proxy is broken.
Why so? Because apparently Jenkins sees the incoming request being on HTTP (the forwarded request) and build its Location header or any other links with HTTP instead of HTTPS (as used by the client browser).

Change By: brenuart (28/Jun/12 6:44 AM)
Resolution: Not A Defect
Status: Resolved Reopened
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to