-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Javed,
On 9/12/2011 10:54 AM, Javed wrote:
> At the end, I circumvented this issue with help of regular
> expressions in urlrewrite filter. I wrote different regular
> expressions to identify jsessionid and converted upper case request
> URI to lower
part but gives problem with
URLRewriteFilter.
>>>>I have used URLRewriteFilter to convert Capital case request URI to
lowercase and SEO purpose.
>>>>The capital case convert rule looks like
> ..
>
>>>>-Javed Attar
>>>>
--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
刘铎,
On 8/4/2011 10:23 PM, 刘铎 wrote:
> I'm using Tomcat 6.0.24. As I know, jsessionid could be returned to
> the tomcat by urlrewriting or cookie. Why not use cookie instead?
In this case, Tomcat cannot determine if cookies are supported, yet, so
the
/y/zz;jsessionid=bce91a85a66aaff384e854d59e5ac877;jsessionid=BCE91A85A66AAFF384E854D59E5AC877
>
> This goes on happening in infinite loop and browser throws error "Page isn't
> redirecting properly"
>
> Can anybody tell me what feature/change in Tomcat 7 r
gt;
> This goes on happening in infinite loop and browser throws error "Page isn't
> redirecting properly"
>
> Can anybody tell me what feature/change in Tomcat 7 responsible for this
> behavior?
> I will really appreciate any
cat 7 responsible for this
behavior?
I will really appreciate any help on this.
Thanks in advance.
-Javed Attar
--
View this message in context:
http://old.nabble.com/Tomcat-7-adds-jsessionid-in-request-URI-as-opposed-to-Tomcat-5-tp32192166p32192166.html
Sent from th
