geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Dillon (JIRA)" <>
Subject [jira] Updated: (GERONIMO-2192) Jetty can't handle encoded urls that contain a jsessionid
Date Thu, 14 Jun 2007 17:36:26 GMT


Jason Dillon updated GERONIMO-2192:

    Component/s: Jetty

> Jetty can't handle encoded urls that contain a jsessionid
> ---------------------------------------------------------
>                 Key: GERONIMO-2192
>                 URL:
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Jetty
>    Affects Versions: 1.1
>         Environment: Geronimo 1.1, Jetty version; Sun JDK 1.5_4, OpenSuSE 10.1, 712 MB
>            Reporter: D. Strauss
>            Priority: Critical
> Hello,
> another testing here was to check if a webapp would still be usable when the user blocks
any cookies from us. JEE typically uses a cookie named JSESSIONID (I think this is specified
somewhere) to identify a user at a web request time. Now, if cookies are blocked, the developers
are instructed to "encode" the urls using the HttpServletResponse.encode() method. Even the
JSTL and c:url use this behaviour (fortunately :P).
> Anyway, today, Jetty had some problems when cookies are blocked. The urls are encoded
at request time, so, a url like
> /register.jspx
> becomes
> /register.jspx;jsessionid=<long hexadecimal value>
> Using Tomcat, everything works as expected (i.e. the user gets identified as long as
he/she uses the session identifier). Jetty, on the other hand, drops the request with a HTTP
404 error telling that it can't find a file named "register.jspx;jsessionid=<long value>".
This is, of course, right. However, it's not the expected behaviour.
> Seems that Jetty can't figure out that this request is encoded ...

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message