[
https://issues.apache.org/jira/browse/TS-3062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Sorber updated TS-3062:
----------------------------
Assignee: (was: Sudheer Vinukonda)
> IMS header incorrectly stripped off for new object fetch even when
> ims_on_client_no_cache is enabled
> ----------------------------------------------------------------------------------------------------
>
> Key: TS-3062
> URL: https://issues.apache.org/jira/browse/TS-3062
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP
> Affects Versions: 5.0.1
> Reporter: Sudheer Vinukonda
> Labels: yahoo
> Fix For: 6.1.0
>
>
> When a client's request includes an IMS header and CC-header indicating
> no-cache (e.g. private, no-store), ATS should add the IMS header in the
> request to the origin when ims_on_client_no_cache setting is enabled and
> ignore_client_no_cache is disabled.
> https://docs.trafficserver.apache.org/en/latest/reference/configuration/records.config.en.html#proxy-config-http-cache-ims-on-client-no-cache
> https://docs.trafficserver.apache.org/en/latest/reference/configuration/records.config.en.html#proxy-config-http-cache-ignore-client-no-cache
> This seems to work as expected for objects already in the cache, but, for a
> new object fetch (object not in cache), ATS is still stripping off the IMS
> header. This behavior is confusing and is not inline with the description of
> the ims_on_client_no_cache setting.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
