[
https://issues.apache.org/jira/browse/WICKET-6170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15294956#comment-15294956
]
ASF subversion and git services commented on WICKET-6170:
---------------------------------------------------------
Commit 3b14e585e0b8a025d2ddcb22d7f74ba5c7cde758 in wicket's branch
refs/heads/wicket-7.x from [~mgrigorov]
[ https://git-wip-us.apache.org/repos/asf?p=wicket.git;h=3b14e58 ]
WICKET-6170 Wrong requestmapper used for cache decorated resources
Undecorate the url before passing it for compatibility score calculation.
> 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
> Assignee: Martin Grigorov
> Fix For: 8.0.0-M1, 7.4.0
>
> 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)
