Yep, this is intentional and spec compliant.
>From the relnotes.html from the JRun 3.1 install:
(Fixed bugs section)
18645 - JRun was improperly encoding path parameters in URLs. The Servlet
2.2 API specification specifies that path parameters are preceded by a
semicolon (for example,
http://www.myserver.com/catalog/index.html;jsessionid=1234). JRun was using
a question mark (for example,
http://www.myserver.com/catalog/index.html?jsessionid=1234). JRun now uses a
semicolon.
- Tormod
-----Original Message-----
From: Johansen, Roar [mailto:[EMAIL PROTECTED]]
Sent: 21. august 2001 09:04
To: JRun-Talk
Subject: URL Rewriting in 3.1
We recently upgraded from JRun 3.02a to 3.1.
I noticed a new behaviour regarding URL rewriting for cookieless session
management:
We use
HttpServletResponse resp;
String originalURL;
String rewrittenURL;
rewrittenURL = resp.encodeURL(originalURL);
Given an originalURL, say "http://www.mydomain.com"; 3.0 would give
"http://www.mydomain.com?jsessionid=9999999999";
Since 3.1, however, the result is
"http://www.mydomain.com;jsessionid=9999999999"; (a semicolon instead of a
question mark). It still works, but it affects our logs, which will now
record each session to a page as different pages. Question: Does anyone know
whether this is intentional or not?
Regards,
Roar :)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
