|
||||||||
|
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'm hitting this one, too, after upgrading to 1.583.
1.583 (Upgraded from 1.559)
OS and version
How was Jenkins installed?
Container and version, if not using the native installer
What's the context path (e.g. / or /jenkins), and what's the URL that fails?
What's the authentication realm (where are the users coming from, Jenkins User Database, LDAP, PAM, ...)
What's the authorization strategy (e.g. matrix auth, logged in users can do anything, ...), and what permissions does anonymous have?
Which client OS and web browser (+ versions of each)?
-What are the exact steps to reproduce this problem in a new browser session (no cookies etc.). Be as precise and exhaustive in these instructions as you can (imagine explaining it to your technologically impaired parents/grandparents/spouse).
1. Load Jenkins login page in an unauthenticated browser session
2. Log in with valid credentials
3. See problem
This can be worked around by removing the ";jsessionid=1qfdq9lhzfvtw10h62t8khybg" part of the URL that hits 404 after login.