https://issues.apache.org/bugzilla/show_bug.cgi?id=49299
Summary: Servlet 3.0 ch.7.1.1 says that custom cookie name
affects URL rewriting
Product: Tomcat 7
Version: trunk
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: normal
Priority: P2
Component: Catalina
AssignedTo: dev@tomcat.apache.org
ReportedBy: knst.koli...@gmail.com
Created an attachment (id=25442)
--> (https://issues.apache.org/bugzilla/attachment.cgi?id=25442)
cookiename.war
In chapter 7.1.1 of servlet-3_0-final-spec.pdf it is said that
"If a web application configures a custom name for its session tracking
cookies, the
same custom name will also be used as the name of the URI parameter if the
session
id is encoded in the URL (provided that URL rewriting has been enabled)."
That is not true for the current trunk: the default "jsessionid" is used
instead.
I am attaching a war file that reproduces this issue.
Steps to reproduce:
1. Deploy it as cookiename.war
2. Access http://localhost:8080/cookiename/
3. Actual result:
The page sends the following cookie:
Set-Cookie: MYSESSIONCOOKIE=658C60E714E9C7C833F4FDA366E0477F; Path=/cookiename;
HttpOnly
but the Reload link on the page uses "jsessionid":
http://localhost:8080/cookiename/index.jsp;jsessionid=658C60E714E9C7C833F4FDA366E0477F
4. Expected result: if that phrase in 7.1.1 is to be followed, I would expect
the Reload link to be
http://localhost:8080/cookiename/index.jsp;MYSESSIONCOOKIE=658C60E714E9C7C833F4FDA366E0477F
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
