[
https://issues.apache.org/jira/browse/TS-4334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15468540#comment-15468540
]
Gancho Tenev commented on TS-4334:
----------------------------------
[~jamesf], I am sorry if I did not make my idea/example clear enough!
I was proposing not to use {{cache_range_requests}} plugin at all and use
{{cachekey}} plugin as your central place of cache key manipulation and then by
using the {{header_rewrite}} plugin to implement the rest of the logic done by
the {{cache_range_requests}} (adding/removing the Range header at different
hooks).
The end result should be practically the same as using {{cache_range_requests}}
plugin but achieved by using more generic plugins (tested it) instead of
hacking into {{cache_range_requests}} which seems pretty specialized and less
configurable.
I was wondering if this would work for you.
Please let me know, I would gladly help you if any problems/concerns.
Cheers!
> The cache_range_requests plugin always attempts to modify the cache key.
> ------------------------------------------------------------------------
>
> Key: TS-4334
> URL: https://issues.apache.org/jira/browse/TS-4334
> Project: Traffic Server
> Issue Type: Improvement
> Components: Plugins
> Reporter: Nolan Astrein
> Assignee: Gancho Tenev
> Fix For: 7.1.0
>
>
> A TrafficServer administrator should be able to specify whether or not the
> cache_range_requests plugin should modify the cache key. The cache key may
> be modified by a previous plugin in a plugin chain and there is no way to
> configure cache_range_requests not to do any further modifications to the
> cache key. Having multiple plugins responsible for cache key modifications
> can cause unexpected behavior, especially when a plugin chain ordering is
> changed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
