[JENKINS-43927] Unable to login due to too many jsessionids creating a too large header

If you use jenkins for a while, you will note that the jsessionid's never expire, and seem to get a new jsessionid.<id> every time.

Over time these build up until the header being sent to the server is so large it can't service the request.

What should happen:

duplicates

JENKINS-25046 Cookie header too long, causing a 413 HTTP error

Michael Neale created issue - 2017-04-28 03:22

Keith Zantow made changes - 2017-04-28 04:52

Link

New: This issue duplicates JENKINS-25046 [ JENKINS-25046 ]

Michael Neale made changes - 2017-04-28 04:58

Resolution		New: Duplicate [ 3 ]
Status	Original: Open [ 1 ]	New: Closed [ 6 ]

Will McKinley made changes - 2018-01-17 16:04

Resolution	Original: Duplicate [ 3 ]
Status	Original: Closed [ 6 ]	New: Reopened [ 4 ]

Josh Soref made changes - 2022-01-24 14:51

Resolution		New: Fixed [ 1 ]
Status	Original: Reopened [ 4 ]	New: Fixed but Unreleased [ 10203 ]

Josh Soref made changes - 2022-01-24 14:51

Status

Original: Fixed but Unreleased [ 10203 ]

New: Resolved [ 5 ]

Jenkins