New HTTP Session Generated For Each Interaction When Cookie-Secure is Enabled
(Doc ID 1277059.1)
Last updated on JULY 06, 2020
Applies to:Oracle WebLogic Server - Version 10.0 and later
Information in this document applies to any platform.
***Checked for relevance on 24-July-2012***
JSESSIONID changes when the application is switched from HTTPS to HTTP. When we enable the SSL port in the WebLogic Server admin console, the session maintains the same session id but when we use the non-SSL port, it generates a new session id with each communication with the browser.
If the application is accessed either on the SSL port or the non-SSL port, there shouldn't be a change in the value of the JSESSIONID.
- Deploy the attached Header application and target it to the AdminServer.
- Make sure that the server is listening in SSL using the demo certs. Disable the HTTP port of WebLogic Server.
- Now, hit the application on the SSL port and you will see the JSESSIONID printed in the Browser. Just keep on pressing F5 and you will see that the JSESSIONID does not change.
- Note the JSESSIONID in a notepad.
- Disable the HTTPS Listen Port for AdminServer and then enable the HTTP Port.
- Now, hit the application on the HTTP port in the same Browser and for every hit on HTTP, you will see that the JSESSIONID keeps changing for every hit.
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