Yes, but if you turn off cookies in the browser and then hit a servlet where
you're using URL rewriting, it still returns the identical string that you
passed to response.encodeURl().
I seem to remember that Tomcat 3.1 had problems with URL rewriting that I
thought were supposed to be fixed in 3.2.1, but I can't get it to work....
--Kyle
-----Original Message-----
From: William Kaufman [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 05, 2001 4:55 PM
To: '[EMAIL PROTECTED]'
Subject: RE: tomcat 3.2.1 and URL rewriting
>From the JSDK 2.2 spec
(
http://java.sun.com/products/servlet/2.2/javadoc/javax/servlet/http/HttpServ
letResponse.html#encodeURL(java.lang.String) ):
Encodes the specified URL by including the session ID in it, or, if encoding
is not needed, returns the URL unchanged. The implementation of this method
includes the logic to determine whether the session ID needs to be encoded
in the URL. For example, if the browser supports cookies, or session
tracking is turned off, URL encoding is unnecessary.
For robust session tracking, all URLs emitted by a servlet should be run
through this method. Otherwise, URL rewriting cannot be used with browsers
which do not support cookies.
-- Bill K.
> -----Original Message-----
> From: Calin Duma [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, April 05, 2001 3:35 PM
> To: [EMAIL PROTECTED]
> Subject: tomcat 3.2.1 and URL rewriting
>
>
> Hello,
>
> I have an issue with URL rewriting - and I could not find an answer in
> the mailing list archive.
>
> Basically when I print out the string returned by a
> response.encodeUrl(..) - it is identical to the original string. I do
> have an http session active.
>
> Any ideeas ?
>
> Thanks,
>
> Calin
>
