http://httpd.apache.org/docs-2.0/mod/mod_headers.html#order tells me: "They are valid in the main server config and virtual host sections, inside <Directory>, <Location> and <Files> sections, and within .htaccess files."
Besides these containers, Apache 2.0 now supports the new <Proxy> container (http://httpd.apache.org/docs-2.0/mod/mod_proxy.html#proxy). So what about using mod_headers to "edit" HTTP headers of content that is just being embedded via ProxyPass? At which position inside the evaluation sequence would <Proxy> appear in this case? I successfully added headers inside a <Proxy> section, so this might be added to the documentation section. I also successfully removed _certain_ other headers, including the "Server:" header (thus masquerading the HTTP response as coming from my own server, when used in combination with "ProxyVia Block"). When I tried to remove certain other headers as well, this didn't work at first. I traced the HTTP traffic of my Apache and saw the (proprietary) header "Fd-Billing-Info: 0" but couldn't remove this one with "Header unset". Then I traced the origin server - and to my surprise I found out that this machine actually sent headers like "Fd_billing_info: 0" (different capitalization, and underscores instead of hyphens), so that mod_proxy (or some other Apache mechanism I am not aware of) seems to have secretly "normalized" these headers in a way that the "Header unset" directive (which works case sensitive, and what about matching "_" to "-"?) surely didn't find what it looked for. After adapting my "Header unset" directives everything went smoothly. This might be worth some note "for the unwary" in the documentation: "You need to specify what Apache received, not what you see Apache made out of it". Regards, Michael --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
