-
Bug
-
Resolution: Fixed
-
Major
-
None
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
-
JSESSION IDs are being managed correctly in Jenkins itself. The session Id expiration on the Jenkins side is being managed by async garbage collector, Cookies use the built-in expiration logic provided by the browser (unless the user explicitly logs out from Jenkins). So IMHO Jenkins manages sessions "like every other app".
Could you please clarify your use-cases? Is it about Blue Ocean?