Chuck Murcko wrote:
> Daniel's hook solves this problem nicely for proxy. Mod_headers is
> symmetric (can do the same ops on its input and output side) now, but
> lacks an efficient way to change its rules on a per request basis. And
> IIUC hooks are in part a method of providing custom processing "taps" in
> a filter chain.
What about a ProxyAddInputFilter and ProxyAddOutputFilter directive that
did the same as the AddOutputFilter and AddInputFilter directives?
These would allow general filters to be added into the proxy origin
filter stack, but will not force proxy-specific behavior.
> If we were designing something intended to be a network node rather than
> a server, something that was as likely to make an outbound connection as
> service an inbound one, I think we would build filters a bit
> differently. But we're not doing that for the general case here. So I
> think the hook is a good solution.
A good solution to what problem? (sorry for being dumb, but I don't
understand why the need to insert request headers before the connection
to the origin server is not met by the RequestHeader directive).
Regards,
Graham
--
-----------------------------------------
[EMAIL PROTECTED] "There's a moon
over Bourbon Street
tonight..."
S/MIME Cryptographic Signature
