[
https://issues.apache.org/jira/browse/TS-4334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15505097#comment-15505097
]
Gancho Tenev commented on TS-4334:
----------------------------------
Checked with [~latesonarinn] offline and here is an excerpt:
9/16/16, 12:06 PM Gancho Tenev:
{quote}
Proposed alternative solution using more generic means (cachekey and
header_rewrite) here: [TS-4334|https://issues.apache.org/jira/browse/TS-4334]
Could you please let me know if it works for you?
{quote}
9/19/16, 9:59 AM Nolan Astrein:
{quote}
Clever solution. I think that will work.
{quote}
[~latesonarinn], could you please verify and/or close this Jira if all looks
good?
(if not please let me know if I can help!)
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)
