Hi;
I am writing a set of RESTful services. client do not send cookies and we
don't want to user URL rewriting for most
of the services (they are just stateless).
The issue is when the client calls http://localhost/services/resource say
n times, the application server/servlet container creates
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Youssef,
Youssef Mohammed wrote:
| I am writing a set of RESTful services. client do not send cookies and we
| don't want to user URL rewriting for most
| of the services (they are just stateless).
| The issue is when the client calls
http://localhos
On Wed, May 14, 2008 at 7:34 PM, Christopher Schultz
<[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> public class SessionKillingRequest
> ~ extends HttpServletRequestWrapper
> {
> ~ public SessionKillingRequest(HttpServletRequest request)
> ~ {
> ~super(re
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Leon,
Leon Rosenberg wrote:
| On Wed, May 14, 2008 at 7:34 PM, Christopher Schultz
| <[EMAIL PROTECTED]> wrote:
|> -BEGIN PGP SIGNED MESSAGE-
|> Hash: SHA1
|>
|>
|> public class SessionKillingRequest
|> ~ extends HttpServletRequestWrapper
|
well, in current tomcat impl ( trunk) it does, but since its an
implementation detail which isn't guaranteed by the api contract of
HttpServletRequest, you probably should capture it explicitely.
regards
Leon
On Thu, May 15, 2008 at 5:42 PM, Christopher Schultz
<[EMAIL PROTECTED]> wrote:
> -B
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Leon,
Leon Rosenberg wrote:
| well, in current tomcat impl ( trunk) it does, but since its an
| implementation detail which isn't guaranteed by the API contract of
| HttpServletRequest, you probably should capture it explicitly.
Excellent point. Tha
