[
https://issues.apache.org/jira/browse/WICKET-5441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846337#comment-13846337
]
Stefan Fussenegger commented on WICKET-5441:
--------------------------------------------
I've submitted [pull request #67 on
github|https://github.com/apache/wicket/pull/67]. There remains a question
though: What is the appropriate caching if versions don't match? The
application default used for my patch still is WebResponse.MAX_CACHE_DURATION
(though at least configurable and only privately cacheable)
> IResourceCachingStrategy implementations should only set caching if version
> matches
> -----------------------------------------------------------------------------------
>
> Key: WICKET-5441
> URL: https://issues.apache.org/jira/browse/WICKET-5441
> Project: Wicket
> Issue Type: Bug
> Affects Versions: 6.12.0, 7.0.0
> Reporter: Stefan Fussenegger
>
> Implementations of IResourceCachingStrategy
> (FilenameWithVersionResourceCachingStrategy and
> QueryStringWithVersionResourceCachingStrategy) should only set cache duration
> to maximum if the version matches. Currently, if a user requests a resource
> with an arbitrary version, the version will be cached for one year
> (WebResponse.MAX_CACHE_DURATION). So people could polute proxy caches with
> potentially upcoming version.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
