|
||||||||
|
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 ... [email protected] (JIRA)
- [JIRA] (JENKINS-14223) accessing Jen... [email protected] (JIRA)
- [JIRA] (JENKINS-14223) accessing Jen... [email protected] (JIRA)
- [JIRA] (JENKINS-14223) accessing Jen... [email protected] (JIRA)
- [JIRA] (JENKINS-14223) accessing Jen... [email protected] (JIRA)
- [JIRA] (JENKINS-14223) accessing Jen... [email protected] (JIRA)
- [JIRA] (JENKINS-14223) accessing Jen... [email protected] (JIRA)
- [JIRA] (JENKINS-14223) accessing Jen... [email protected] (JIRA)
- [JIRA] (JENKINS-14223) accessing Jen... [email protected] (JIRA)
- [JIRA] (JENKINS-14223) accessing Jen... [email protected] (JIRA)

True - this is what was causing issues in our setup as well (Apache front-end with SSL forwarding to Jenkins on the local host).
We had to play with Apache rewrite rules to solve it - pay special attention to the Location response header, this is where everthing starts if I remember properly.