|
||||||||
|
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 |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
I have this problem also, no apache proxy involved. It happens when trying to log into jenkins directly. If I access jenkins at a different hostname then I able to log in and not get a redirect back to the log in page.
For example, if my jenkins server is at jenkins.my.example.com:8080 and I get this erroneous redirect, if I try to access it at jenkins.my:8080 (and let my resolver append example.com) then it works. This is simply because to chrome "jenkins.my.example.com" and "jenkins.my" are different servers and it stores the data from them separately.
So this smacks of a cookies problem, right? You'd think. But I have tried clearing all of the cookies in chrome for jenkins.my.example.com and the problem persists.
If I start chrome with a brand-new $HOME it also works fine.
Clearly there is something in chrome that is preventing this from working, but what? My next step would normally be to sniff the HTTP protocol between working and not working and see what is different, but alas, this is all over SSL, so that won't help.![]()
Any other ideas?