[
https://issues.apache.org/jira/browse/WICKET-3921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13071662#comment-13071662
]
Martin Grigorov commented on WICKET-3921:
-----------------------------------------
Hi Timo,
Does that mean that if we move the setting of cache related headers before the
redirect in AjaxRequestTarget#respond(RequestCycle) the problem will be solved ?
That's why I need failing case to verify that the fix works.
> No HTTP response cache headers are set in Wicket Ajax redirects
> ---------------------------------------------------------------
>
> Key: WICKET-3921
> URL: https://issues.apache.org/jira/browse/WICKET-3921
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core
> Affects Versions: 1.4.17
> Reporter: Timo Weber
> Priority: Minor
>
> Usually HTTP response cache headers are being set in AjaxRequestTarget for
> Ajax responses. But for redirects, the handling is done in WebResponse where
> no cache headers are being set, which could lead to some trouble.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
