mlibbey commented on issue #1417: URL: https://github.com/apache/trafficserver/issues/1417#issuecomment-1168915678
Realistically, with the current toolset, I think the only way around getting purge with authproxy is to create a different "dummy" remap rule that - generates the same cache key as the authproxy one - limits the accepted method to purge (to prevent circumventing the authorization) So like (not tested) map http://examplecompurge.localhost:8080 https://example.com/ @action=allow @method=PURGE (assuming that the cachekey of your authproxy rule has a host name of example.com ... if not, need some more conf_remap, or cachekey plugin configs) Then your purge for localhost:8080/foo/bar would be a request to http://examplecompurge.localhost:8080/foo/bar ... which would hit the second map rule, and thus it wouldn't be proxied to the auth server. I suppose a second version which would be awesome to test would be to get your auth server to always return 200 to PURGE method. Guessing that might let the purge to proceed past the plugin, and into the ATS internals. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
