[jira] [Comment Edited] (TS-4334) The cache_range_requests plugin always attempts to modify the cache key.

["James Fang (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TS-4334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15466981#comment-15466981 ] 

James Fang edited comment on TS-4334 at 9/6/16 9:41 AM:
--------------------------------------------------------

it seems to me that cache key can only be set once ? on 6.2.0.

reason:
1) in TSCacheUrlSet, it check if cache url is NULL
2) from my testing, ( cachekey.so cache_range_requests.so, in this order in remap.config ),
    there is the following error log:
   [Sep  6 09:30:55.813] Server {0x2b5221c5ffc0} DIAG: (cache_range_requests) [cache_range_requests.cc:110] range_header_check(): failed to change the cache url to
    indicates that changing of cache url failed. 


was (Author: jamesf):
it seems to me that cache key can only be set once ?

reason:
1) in TSCacheUrlSet, it check if cache url is NULL
2) from my testing, ( cachekey.so cache_range_requests.so, in this order in remap.config ),
    there is the following error log:
   [Sep  6 09:30:55.813] Server {0x2b5221c5ffc0} DIAG: (cache_range_requests) [cache_range_requests.cc:110] range_header_check(): failed to change the cache url to
    indicates that changing of cache url failed. 

> 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)