httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nick Gearls <nickgea...@gmail.com>
Subject Re: mod_proxy & headers
Date Mon, 02 May 2011 10:56:10 GMT
It's indeed prior to 2.2.12. I assume the problem is solved.

However, what about the proposition to indicate for every module (or 
directive when needed) the phase it runs, to be able to determine 
interactions? I guess this shouldn't be difficult when you know the 
module. This could maybe even be generated automatically from the code?

And maybe also specific features, like SetEnv result that cannot be used 
by other modules whereas SetEnvIf result can.

This would be a major help in some cases.

Regards,

Nick


-------- Original Message --------
Subject: RE: mod_proxy & headers
Date: Mon, 2 May 2011 12:28:50 +0200
From: "Plüm, Rüdiger, VF-Group" <ruediger.pluem@vodafone.com>
Reply-To: dev@httpd.apache.org
To: <dev@httpd.apache.org>



> -----Original Message-----
> It seems that some headers cannot be modified when mod_proxy
> sets them.
> Ex: Content-Type - it is not possible to overwrite it with any of the
> following directives:
>    AddType ...
>    ForceType ...
>    Header set ...

Which version did you use where Header set Content-Type failed?
It does not work correctly before 2.2.12.

Mime
View raw message