-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major
-
Component/s: core
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:Â
- I should be able to log into jenkins
- Jessionid should be like every other app serverÂ
- duplicates
-
JENKINS-25046 Cookie header too long, causing a 413 HTTP error
-
- Open
-