|
||||||||||||||
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 |
- [JIRA] (JENKINS-14223) accessing Jenkins ... di...@fast.au.fujitsu.com (JIRA)
- [JIRA] (JENKINS-14223) accessing Jen... brenu...@java.net (JIRA)
- [JIRA] (JENKINS-14223) accessing Jen... di...@fast.au.fujitsu.com (JIRA)
- [JIRA] (JENKINS-14223) accessing Jen... ohtake_tomoh...@java.net (JIRA)
- [JIRA] (JENKINS-14223) accessing Jen... brenu...@java.net (JIRA)
- [JIRA] (JENKINS-14223) accessing Jen... k...@kohsuke.org (JIRA)
- [JIRA] (JENKINS-14223) accessing Jen... k...@kohsuke.org (JIRA)
- [JIRA] (JENKINS-14223) accessing Jen... brenu...@java.net (JIRA)
- [JIRA] (JENKINS-14223) accessing Jen... brenu...@java.net (JIRA)
- [JIRA] (JENKINS-14223) accessing Jen... di...@fast.au.fujitsu.com (JIRA)
There is still a case not working properly though...
Suppose the following setup:
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).