My Oracle Support Banner

JSESSION Cookie Path Would Set Incorrectly to “/” with WLS Patch Bundle (Doc ID 2970732.1)

Last updated on AUGUST 31, 2023

Applies to:

Oracle WebLogic Server - Version and later
Information in this document applies to any platform.


On : version

WebLogic Server has the ability to assign a session cookie (JSESSIONID) to web applications to enable the web applications to "remember" users when they move between webpages. By specifying the cookie name using the CookieName parameter and the cookie path with the CookiePath parameter, defined in the WebLogic-specific deployment descriptor weblogic.xml <session-descriptor> element, the web application can authenticate users and persist the web session of requests and responses between client and server.  If the cookie path is not defined in the weblogic.xml, the JSESSION cookie path is normally expected to be picked up from the weblogic-application.xml file.

The behavior of the JSESSION cookie path changes after the application of the WLS Patch Bundle  After applying WLS Patch Bundle, the cookie-path sets incorrectly to “/” when no directive exists in weblogic.xml.




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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.