[jira] [Commented] (TS-4464) authproxy (as remap plugin) turns off cache for internal requests without discretion

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

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

James Peach commented on TS-4464:
---------------------------------

IIRC this is what {{AuthRequestIsTagged}} was meant to do.

> authproxy (as remap plugin) turns off cache for internal requests without discretion
> ------------------------------------------------------------------------------------
>
>                 Key: TS-4464
>                 URL: https://issues.apache.org/jira/browse/TS-4464
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Plugins
>            Reporter: Leif Hedstrom
>
> If you use authproxy together with another plugin which also wants to do an internal request, you end up turning off the cache without discretion. This means that using e.g. authproxy together with background_fetch, the request the background_fetch generates (and goes through the same remap rule) can not be cached.
> There's an easy fix that takes care of this case when using authproxy as a remap plugin. I'm not sure how we'd do it if you use the authproxy as a global plugin.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)