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/04/30 21:28:16 UTC

[jira] [Resolved] (WICKET-5166) Relax the requirements for using FilteringHeaderResponse

     [ https://issues.apache.org/jira/browse/WICKET-5166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Grigorov resolved WICKET-5166.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 7.0
                   6.8.0
    
> Relax the requirements for using FilteringHeaderResponse
> --------------------------------------------------------
>
>                 Key: WICKET-5166
>                 URL: https://issues.apache.org/jira/browse/WICKET-5166
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>    Affects Versions: 6.7.0
>            Reporter: Martin Grigorov
>            Assignee: Martin Grigorov
>             Fix For: 6.8.0, 7.0
>
>
> I see two improvements to FilteringHeaderResponse:
> 1) FilteringHeaderResponse requires a name for the filter that should be used for contributions in the <head>. Since the value of this filter name is custom FilteringHeaderResponse can provide constructor which provides default name for this filter
> 2) If a HeaderItem is not accepted by any of the configured filters then the item is simply dropped and a warning message is logged. It will be much more friendlier if the item is rendered in the <head> as in the case when non-filtering header response is used. The application should not be forced to provide filter for this explicitly. 

--
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