Re: mod_proxy patches for HTTP Header manipulation

Joshua Slive writes:
> On Mon, 21 May 2001, Kwindla Hultman Kramer wrote:

> > RequestHeader set Language fr %{HTTP_HOST} ^fr
> >
>
> Just before people go wild with this sort of thing, please consider
> not inventing a new syntax for conditional directives. We already
> have CustomLog/Allow/Deny which get along well with the env=
> syntax, as in:
>
> SetEnvIf Host ^fr french
> RequestHeader set Lanuage fr env=french
>
> (I don't have much sympathy for the "all in one directive" argument when
> there is existing code and knowledge that can be more efficiently used.)
>

Absolutely. I stand corrected. As far as conditionals go, an 'env=' syntax does everything I would want, and is much more consistent with other modules. (It would solve Ian's problem, for example.)

To push this a little further: it could be nice to be able to use both environment variables and mod_rewrite-style connection info variables as part of the Header directive's set-string. Perhaps something like:

  RequestHeader set Language %{ENV:fr}   RequestHeader set X-Forwarded-For %{REMOTE_ADDR}

Is this more reasonable than my last suggestion <laugh>.

Kwindla Received on Mon May 21 22:15:33 2001

Do you need help?

In addition to our free technical library, Pantek provides professional IT services to companies who utilize Open Source software: Learn more about Pantek's Technical Support offerings Place an order for 24/7/365 Technical Support here Learn more about Pantek, who we are, and what we do Chat with a Live Operator Related httpd.apache.org Links announce bugs cvs dev docs gui-dev modproxy-dev packagers testers Request more information about Pantek