My Oracle Support Banner

Session Lost when Cookieless Browser used on URL Ending With a "/" and ";jsessionid" (Doc ID 1336906.1)

Last updated on FEBRUARY 02, 2024

Applies to:

Oracle GlassFish Server - Version 3.0 to 3.1 [Release 3.0 to 3.1]
Information in this document applies to any platform.


On GlassFish version 3.0 and 3.1, a user's HTTP session may be lost when accessing an application. For example, when a user visits or gets redirected to a top-level application page such as http://host:port/webapp/ using a cookieless browser, they will always lose the HTTP session that was initially created.

Typically for an application that has been written to support access from browsers that don't support cookies,  once the web application creates a new HTTP session, the generated the web pages will have encoded URLs of the form "page.jsp;jsessionid=xxxx".  The problem is that when these encoded URLs are accessed, the HTTP session is not retained and is lost.

A common environment where this problem can be encountered is where a web application has been written to be accessed over the Wireless Access Protocol (WAP), for example from a web browser embedded in a mobile phone.




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.