[Bug 63282] Cache keys incorrect on rewrite

[bu...@apache.org]

https://bz.apache.org/bugzilla/show_bug.cgi?id=63282

--- Comment #4 from Raphaël Droz <ra...@gmail.com> ---
Use-case about caching the response of a request forwarded upstream.

Example:

ProxyRequests On
<Location "/apiproxy">
RewriteEngine    On
RewriteRule ^ "https://upstream/?param=value" [P,L]
RequestHeader set Authorization "Basic foobar"
</Location>

We want to cache using /apiproxy as a cache-key and
- disregard the rewritten URL (and its query-string)
- disregard the fact that the forwarded request was passed an additional
Authorization header


The only way we can control the location of mod-cache is through
SetOutputFilter
But :
- Neither does it provide control about using the original vs the rewritten URL
- Neither does it provide stage selection (before/after/between)
Request/Response headers modification.


This cache-key fine-tuning and pipeline positioning are probably the main
aspects keeping mod-cache growing from toy/poc to a mature module.

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org