Hi Jeff,
Thanks for your response.
I'd like the ability to set HTTP response headers coming from a webapp (which is fronted by Apache -- the same instance / process where MPS is running) just before MPS sees them, to "patch them up", so to speak.
One example would be a dynamic HTML response from the webapp which includes restrictive cache-control resp headers, eg "private", which I understand would prevent MPS from optimizing it.
I want the webapp to keep indicating intended (non)cacheability, but to allow MPS to do its work on the page.
Specific example:
webapp says "max-age=0" -> [TBD apache-based fixup changes this to max-age=300] -> MPS sees max-age=300 (which it interprets and remembers as a 5-min TTL) and optimizes the page, then sets its standard cache-related resp headers (ie max-age=0) and passes it down -> proxies -> browsers.
Until/unless the webapp is updated to rely on MPS to handle Cache-control responses on its behalf, I want to edit the headers (in Apache, in conf assoc w/ MPS presence) to allow MPS to do its work.
In a similar vein, there are some resp headers I'd like to edit just AFTER mps is done rewriting, but before the resp goes down the wire.
Other use cases include normalizing overly-broad "Vary" responses; accounting for non-standard proxies (like Akamai); etc.
I'm fluent w/ mod_rewrite, mod_headers, ap24 expr etc... but not with the deepest aspects of internal tables and other arcana.
Is it possible to do this kind of fixup?
I'm hopeful others have encountered these use cases...
Thanks in advance for any experiences / insights here!
Sincerely,
Chris