[
https://issues.apache.org/jira/browse/WICKET-4609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Grigorov updated WICKET-4609:
------------------------------------
Attachment: crypto-demo.tgz
Here is a demo app that shows that urls to .css resources are properly created
with and without jsessionid.
Please modify it and re-attach if there are problems and we will reopen the
ticket.
> Javascript header references without cookies with CryptoMapper not working
> --------------------------------------------------------------------------
>
> Key: WICKET-4609
> URL: https://issues.apache.org/jira/browse/WICKET-4609
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.5.5
> Environment: Windows 7 64-bit
> IE 9, FF 12
> Jetty 6, WebSphere AS 7
> Reporter: David Rain
> Labels: cookies, cryptomapper, header-contribution, javascript,
> reference, wicket
> Attachments: crypto-demo.tgz
>
>
> Preconditions:
> - disabled cookies
> - CryptoMapper enabled (set as root mapper)
> When contributing Javascript (CSS contributions are affected too) to head,
> URLs are rendered WITHOUT jsessionid. Thus CryptoMapper can't find its key in
> session when cookies are disabled. This affects wicket-ajax.js contribution
> in AbstractDefaultAjaxBehavior too! So Wicket is not working at all.
> I found out, that in HeaderResponse#internalRenderJavaScriptReference is line:
> String urlWoSessionId = Strings.stripJSessionId(url);
> which strips session id (that was previously encoded into by
> HttpServletResponse) from URL explicitly. I wonder WHY? Does the jsessionid
> parametr in URL break something else?
> internalRenderCSSReference method is affected too.
--
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
