Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
Jenkins 1.581, launched through the built in Jetty
-
-
Jenkins 2.184
Description
Each time Jenkins (re)starts, its session-cookie name changes (ie JSESSIONID.some_random_string).
After a while, the browser have a bunch of session cookies, each one having a different name, causing the "Cookie" request header to be very long. The server returns a HTTP 413 response and a blank page. The user must clean his cookies in order to access Jenkins again.
Workaround: Since Jenkins 2.66 there are custom options for managing Jetty session IDs: https://github.com/jenkinsci/extras-executable-war/#jetty-session-ids
Attachments
Issue Links
- is duplicated by
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Closed
-
- is related to
-
JENKINS-44894 Make Jetty Session ID configurable via System properties
-
- Resolved
-
- links to
Activity
Dmitry Mikhirev
added a comment - > The code fix did work and was fine for more than enough time.
Again, it is not a fix, it is just a workaround that does not work with default settings.
> A change to that code would be a significant behavior change and would not have the same summary as this ticket.
It is not a significant change, just adding couple lines of code. Try to load a stored ID, if not successful generate a new one and store it.
Dmitry Mikhirev
added a comment - > The code fix did work and was fine for more than enough time.
Again, it is not a fix, it is just a workaround that does not work with default settings.
> A change to that code would be a significant behavior change and would not have the same summary as this ticket.
It is not a significant change, just adding couple lines of code. Try to load a stored ID, if not successful generate a new one and store it. Dmitry Mikhirev
added a comment - reopen bizdelnick as requested by jsoref, please open a new issue. Reopening this issue is not helping you get a fix and is not helping others.
I am acting in my role as a member of the Jenkins board by making this request. I believe that the request from Josh to open a new ticket is reasonable.
Dmitry Mikhirev
added a comment - I won't stop reopening this issue. There were issues opened by other users about this bug that were closed as duplicates of this one, so I conclude filing a new issue does not work.
The bug, reported here, was not fixed. The provided workaround "if you don't want this happen to you, go change your system properties" is not acceptable.
Dmitry Mikhirev
added a comment - I won't stop reopening this issue. There were issues opened by other users about this bug that were closed as duplicates of this one, so I conclude filing a new issue does not work.
The bug, reported here, was not fixed. The provided workaround "if you don't want this happen to you, go change your system properties" is not acceptable.
A change to that code would be a significant behavior change and would not have the same summary as this ticket.