|
|
| Applications |
| Mailing Lists |
| Miscellaneous |
| Operating Systems |
| Programming |
Re: mod_proxy patches for HTTP Header manipulation
Date: Sun May 20 2001 - 12:02:44 EDT
> 1) It is not as flexible as one might like -- in particular, I added
> an optional pattern-match field which is matched against the
> request uri. If the uri satisfies the pattern match, the header
> directive is applied. If not, not.
What kind of pattern match field are you talking about?
The header changes can be limited to certain places using RequestHeader inside <Location> directives. Is this enough for your application?
> 2) It only works on the incoming headers. I wrote code to supply
> symmetrical directives that set both incoming and outgoing headers.
The original only worked on outgoing headers, but made the changes before the content handler ran, which was pretty useless if you wanted to change headers coming from a remote server.
> 3) It is not clear how mod_headers and mod_proxy should work
> together. Both modules implement fixup handlers. Potential ordering
> problems or other conflicts seem not unlikely.
The actual work in proxy was always done in a handler, not a fixup (which was there to kludge a way for forward proxies to work without script handlers getting in the way), but because the headers fixup always ran before the proxy handler it was useless. This is now fixed...
> CacheFreshenDate, if 'On', sets the Date header to be current when a
This is something I will add to the new mod_cache.
> ProxyResponseExpiresVector allows one to decouple the internal
This also belongs in mod_cache.
Regards,
Graham
-- ----------------------------------------- minfrin@sharp.fm "There's a moon over Bourbon Street tonight..."
- application/x-pkcs7-signature attachment: S/MIME Cryptographic Signature
This archive was generated by hypermail 2.1.8 : Thu Aug 24 2006 - 14:53:16 EDT
|
Contact Us Legal Notices Order Services Online Pantek Home Privacy Policy IT news Site Map Pantek Library |