JSESSIONID Set With An Expiry Date That Does Not Get Extended In Spite Of Activity
(Doc ID 2582982.1)
Last updated on DECEMBER 16, 2023
Applies to:Oracle WebLogic Server - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
Some of the pages on web application is protected which will send the user a 302 response when we try to access a protected resource prior to authenticating the user. In these cases the JSESSIONID is being set with an expiry date:
JSESSIONID=xxxxxx; expires=Fri, 16-Aug-2019 19:21:01 GMT; path=/; HttpOnly
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document