[TS-3350] Turning off cache in remap rule has unexpected Proxying cases

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 5.1.0
• Fix Version/s: 7.1.0
• Component/s: Configuration, Core
• Labels: A C
• Assignee: Gancho Tenev
• Reporter: Miles Libbey
• Created: 29/Jan/15 23:38
• Updated: 08/Sep/16 15:31

Description

We are using
@plugin=conf_remap.so @pparam=proxy.config.http.cache.http=0
in a remap rule.

We see 2 unexpected proxying cases:
1) Cache-control: only-if-cached.
Normally a request with this header will only return a 200 if the object is cached (504 if not cached). We always get a 200 OK for these urls, suggesting the request is forwarded to the origin. (If the X-Debug plugin is installed, and X-Debug:X-Cache is also sent, the response indicates the cache was skipped.

2) PURGE.
When we issue a PURGE request for urls matching this remap, it appears that the PURGE is proxied to the origin server.

Issue Links

• is duplicated by: TS-3594 Trafficserver proxying PURGE request when cache is turned off