[jira] [Commented] (WICKET-6170) Wrong requestmapper used for cache decorated resources

["Martin Grigorov (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WICKET-6170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15294890#comment-15294890 ] 

Martin Grigorov commented on WICKET-6170:
-----------------------------------------

Your quickstart doesn't reproduce the described issue.
I get 404 for both urls (I needed to add port 8080).

> Wrong requestmapper used for cache decorated resources
> ------------------------------------------------------
>
>                 Key: WICKET-6170
>                 URL: https://issues.apache.org/jira/browse/WICKET-6170
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 7.3.0
>            Reporter: Sverre Boschman
>            Priority: Critical
>         Attachments: wicket-resourcemapper.zip
>
>
> Introduced with the fix for WICKET-6094.
> ResourceMapper.getCompatibilityScore now returns the score of AbstractBookmarkableMapper.getCompatibilityScore minus 1. Unfortunately AbstractBookmarkableMapper.getCompatibilityScore does not remove any caching decoration from the request url and will always return 0. So the score for the ResourceMapper that should handle the request is -1, and e.g. the HomePageMapper with a score of 0 will handle the request.
> Example:
> GET http://localhost/stylesheet.css -> stylesheet
> GET http://localhost/stylesheet-ver-xxxx.css -> homepage
> Somehow ResourceMapper.removeCachingDecoration should be used during getCompatibilityScore.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)