blockquote, div.yahoo_quoted { margin-left: 0 !important; border-left:1px
#715FFA solid !important; padding-left:1ex !important; background-color:white
!important; } Hmm..it should be possible to do what you need with a plugin.
For instance, going back to the solution you tried, perhaps you could instead
of storing the CC headers in the Request context, rename them with custom names
in the Response context (which should get cached) and rename them as required
subsequently?
"1. In TS_HTTP_READ_RESPONSE_HDR_HOOK, remove Expires and
Cache-Control: max-age headers and keep the values in the request
context.
2. In TS_HTTP_SEND_RESPONSE_HDR_HOOK, restore Expires and
Cache-Control: max-age headers with the values stored in the request
context."
On Thursday, May 12, 2016, 7:14 PM, Hiroaki Nakamura <hnaka...@gmail.com> wrote:
I tried and found that when I modify headers in TS_HTTP_READ_RESPONSE_HDR_HOOK,
the cached object has those modified headers, so when the next time a
request comes in,
the cached response with the modified headers is served.
This is not what I want. My requirement is to serve cached objects
with the original headers.
I think it cannot be done with a plugin.
So here I propose my request for modification again.
> How about adding a value to proxy.config.http.cache.required_headers?
> https://docs.trafficserver.apache.org/en/latest/admin-guide/files/records.config.en.html#proxy-config-http-cache-required-headers
>
> 0 = no headers required to make document cacheable
> 1 = either the Last-Modified header, or an explicit lifetime header,
> Expires orCache-Control: max-age, is required
> 2 = explicit lifetime is required, Expires or Cache-Control: max-age
> 3 (new value) = explicit lifetime is required, Cache-Control: s-maxage
> (Expires or Cache-Control: max-age are ignored).
Please give me your feedbacks.
Regards,
Hiroaki
