-
Bug
-
Resolution: Unresolved
-
Major
-
Jenkins 1.581, launched through the built in Jetty
-
-
Jenkins 2.184
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
- is duplicated by
-
JENKINS-36880 WARNING: badMessage: 413 for HttpChannelOverHttp and WARNING: Header is too large >8192
-
- Resolved
-
-
JENKINS-36993 Cookie header too long, causing a 413 HTTP error
-
- Resolved
-
-
JENKINS-43927 Unable to login due to too many jsessionids creating a too large header
-
- Resolved
-
-
JENKINS-73428 Unable to follow output of jenkins job
-
- Resolved
-
-
JENKINS-45449 "Bad Message 431" everywhere
-
- Closed
-
- is related to
-
JENKINS-44894 Make Jetty Session ID configurable via System properties
-
- Resolved
-
- links to
[JENKINS-25046] Cookie header too long, causing a 413 HTTP error
Attachment | New: 413_on_requests.png [ 30062 ] | |
Attachment | New: full_of_session_cookie.png [ 30063 ] |
Priority | Original: Major [ 3 ] | New: Critical [ 2 ] |
Labels | New: 2.0 |
Priority | Original: Critical [ 2 ] | New: Minor [ 4 ] |
Labels | Original: 2.0 |
Same problem here, request information screenshots attached.