You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2013/08/06 15:57:47 UTC
[jira] [Resolved] (WICKET-5304) AbstractResource should check for
error code first before for modifications
[ https://issues.apache.org/jira/browse/WICKET-5304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov resolved WICKET-5304.
-------------------------------------
Resolution: Fixed
Fix Version/s: 6.10.0
7.0.0
> AbstractResource should check for error code first before for modifications
> ---------------------------------------------------------------------------
>
> Key: WICKET-5304
> URL: https://issues.apache.org/jira/browse/WICKET-5304
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 6.9.1
> Reporter: Martin Grigorov
> Assignee: Martin Grigorov
> Priority: Minor
> Fix For: 7.0.0, 6.10.0
>
>
> Since org.apache.wicket.request.resource.AbstractResource#setResponseHeaders() gives a chance to the application to set custom headers it should first check for error and status codes set and then check for modifications (Not Modified).
> Because now one needs to reset the modification time of the resource if she wants to set error or status code.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira