Quantcast

stateless resources vs. no cookies

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

stateless resources vs. no cookies

Jan Loose
Hi,

I found this problem in Wicket 1.4.20:

Let's have a browser without cookies enabled. We use stateless resources - there is no jsessionid rendered - it is always removed in WebRequestCodingStrategy#390 - this is OK, we want to cache it during the first request and we don't know the session is requestet via cookie or parameter). But when the browser makes a request to this resource, then there is requested a session, that doesn't exist.

RequestLogger#229 (the method requestTime should work without usage of session in this case)
WicketFilter#1197 (if the resource is cacheable then the session is obtained, why?)

What is the reason for this? Has anybody idea how to fix it/workaround it?

Thank you very much,
Jan

--
Jan Loose
J2EE Team Leader / Senior J2EE Developer
_____________________________________________
Cleverlance – CREATE IT
člen Cleverlance Group
www.cleverlance.com

Dukelských hrdinů 34
170 00 Praha 7
Czech Republic

Tel: +420 266 177 166
Mobil: +420 777 788 078
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: stateless resources vs. no cookies

Martin Grigorov-4
Hi,

Please use users@ mailing list for such kind of questions.
Also please re-phrase your question because I personaly find it
confusing and I cannot help you.

On Wed, Jun 13, 2012 at 7:39 PM, Jan Loose <[hidden email]> wrote:

> Hi,
>
> I found this problem in Wicket 1.4.20:
>
> Let's have a browser without cookies enabled. We use stateless resources -
> there is no jsessionid rendered - it is always removed in
> WebRequestCodingStrategy#390 - this is OK, we want to cache it during the
> first request and we don't know the session is requestet via cookie or
> parameter). But when the browser makes a request to this resource, then
> there is requested a session, that doesn't exist.
>
> RequestLogger#229 (the method requestTime should work without usage of
> session in this case)
> WicketFilter#1197 (if the resource is cacheable then the session is
> obtained, why?)
>
> What is the reason for this? Has anybody idea how to fix it/workaround it?
>
> Thank you very much,
> Jan
>
> --
> Jan Loose
> J2EE Team Leader / Senior J2EE Developer
> _____________________________________________
> Cleverlance – CREATE IT
> člen Cleverlance Group
> www.cleverlance.com
>
> Dukelských hrdinů 34
> 170 00 Praha 7
> Czech Republic
>
> Tel: +420 266 177 166
> Mobil: +420 777 788 078



--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
Loading...