James Fang updated TS-4334:
    Comment: was deleted

(was: cache_range_local.config  will change a 200 status to 206, so we may need 
add another condition:

cond %{CLIENT-HEADER:Range} AND         # only match range request
cond %{STATUS} =200
set-status 206

> 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

Reply via email to