[
https://issues.apache.org/jira/browse/WICKET-4334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187566#comment-13187566
]
Chris Colman commented on WICKET-4334:
--------------------------------------
While it's great wicket now renders static resource links without jsessionidS
when such a resource is requested Wicket still attempts to establish a session
when servicing requests for such a static resource according to the stack trace.
I analyzed the stack trace and there is no direct attempt to explicitly
establish a session but there is an implicit session establishment via a call
to getSessionId. I doubt that call is needed to service a request for static
resource.
I wasn't sure if this should be entered as a separate issue or a continuance of
this one.
> Prevent Wicket from causing redundant download of stateless resources (.js,
> .css etc.,) on browser with cookies enabled
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: WICKET-4334
> URL: https://issues.apache.org/jira/browse/WICKET-4334
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.4.19, 1.5.4
> Environment: Client browser with cookies enabled.
> Reporter: Chris Colman
> Assignee: Martin Grigorov
> Labels: performance, wicket
> Fix For: 1.5.4, 6.0.0
>
>
> A jsessionid is added to package resource links of the first page visited,
> most of which are static and don't need session info for them to be rendered.
> For a new session in a browser with cookies enabled this causes a 'double
> load' of every package resource: once for the initial page (with jsessionid
> added) and again for the subsequent page (with no jsessionid added).
> Each time the user revisits the site with their previous session expired
> another (redundant) download of the package resources will occur (because
> they have a different jsessionid suffix)
> Examining the IE cache we can see that both the jsessionid suffixed version
> and the version without the jsessionid suffix have both been cached as it
> treats each as individual resources.
> This will cause a performance hit for users visiting a Wicket site for the
> first and subsequent times (after cookie expiration) on most average ADSL
> connections and might have an impact on bandwidth demand/cost on extremely
> busy Wicket powered web servers.
> Possible solution:
> Wicket always renders stateless resources without any jsessionid regardless
> of whether the page is stateful or stateless. When servicing a request for a
> resource without a jsessionid Wicket does not attempt to establish a session
> which avoids creating a Session on every stateless resource request.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
