> On Dec 6, 2017, at 7:11 AM, Benjamin Morel <[email protected]> wrote:
>
> Hi guys, I'm using ATS as a forward proxy, to provide a local cache to my
> application.
> When accessing a private file on Amazon S3, an Authorization header is sent,
> and ATS does not cache the response.
>
> This is clearly documented
> <https://docs.trafficserver.apache.org/en/latest/admin-guide/configuration/cache-basics.en.html#client-directives>:
>
> By default, Traffic Server does not cache objects with the following request
> headers:
> Authorization
> Cache-Control: no-store
> Cache-Control: no-cache
> To configure Traffic Server to ignore this request header, refer to
> Configuring Traffic Server to Ignore Client no-cache Headers
> <https://docs.trafficserver.apache.org/en/latest/admin-guide/configuration/cache-basics.en.html#configuring-traffic-server-to-ignore-client-no-cache-headers>.
>
> I followed the only suggestion in the documentation:
>
> CONFIG proxy.config.http.cache.ignore_client_no_cache INT 1
>
> But this still does not make it ignore the Authorization header, as far as I
> can see.
> Plus, I do not want to ignore the Cache-Control header, just Authorization.
>
> Is there a configuration entry to make ATS ignore the Authorization header?
Well, with CC: no-store, no-cache, ATS is not going to write to cache (and not
serve out of cache). It also doesn’t know how long to cache even if you did
remove those (unless you enable the lifetime heuristic options).
That much said, for the Authorization part, you likely have to do
CONFIG proxy.config.http.cache.ignore_authentication INT 1
— Leif
