stateless resources vs. no cookies

[Jan Loose <ja...@cleverlance.com>]

Hi,

I found this problem in Wicket 1.4.20 if cookies are disabled.

If there is used a stateless resource then no jsessionid is rendered. It  
is removed on the line 390 of the class WebRequestCodingStrategy. I hope  
this is OK.

Once the browser makes a request to this resource, then there is created a  
new session, because there is no jsessionid - neither defined by cookie  
nor defined by the URL.

The class RequestLogger, line 229 - from my point of view the method  
'requestTime' shouldn't work with the session in this case.
The class WicketFilter, line 1197 - if the resource is cacheable then the  
session is obtained, why? The problem is that there is no session because  
no jsessionid is defined.

What is the reason for this? Does anyone have any idea how to fix it/do a  
workaround?

Thank you very much,
Jan

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org

Re: stateless resources vs. no cookies

[Martin Grigorov <mg...@apache.org>]

Hi,

Wicket creates temporary o.a.w.Session object only if Session.get() is
called during the request lifecycle.
Until you call Session().get().bind() no javax.servlet.HttpSession
will be created and Wicket's Session will be garbage collected at the
end of the request processing.

On Wed, Jun 13, 2012 at 10:39 PM, Jan Loose <ja...@cleverlance.com> wrote:
> Hi,
>
> I found this problem in Wicket 1.4.20 if cookies are disabled.
>
> If there is used a stateless resource then no jsessionid is rendered. It is
> removed on the line 390 of the class WebRequestCodingStrategy. I hope this
> is OK.
>
> Once the browser makes a request to this resource, then there is created a
> new session, because there is no jsessionid - neither defined by cookie nor
> defined by the URL.
>
> The class RequestLogger, line 229 - from my point of view the method
> 'requestTime' shouldn't work with the session in this case.
> The class WicketFilter, line 1197 - if the resource is cacheable then the
> session is obtained, why? The problem is that there is no session because no
> jsessionid is defined.
>
> What is the reason for this? Does anyone have any idea how to fix it/do a
> workaround?
>
> Thank you very much,
> Jan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>



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

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org