Please add one more config option - setenv.add-or-replace-response-header.
This one will be very useful, because add-response-header really adds, but not replaces header.
directives to set value, rather than append values to headers, env
These directives take precedence over the setenv.add-* counterparts
Set a blank value for request or response header to remove the header
(blank value in environment will be set as the value; not removed)
setenv.*-environment is now deferred to handle_request_env hook.
setenv.*-response-header is now processed in handle_response_start hook.
#1 Updated by Anonymous over 9 years ago
A list might be enough, but I used this change extensively to do really intelligent filtering on a project where I got hundreds of notifications a day. It was far easier to setup filters for specific headers; parsing (especially with server side filtering agents like Sieve) might be much harder. Besides, aren't headers pretty well understood?
- Description updated (diff)
- Status changed from New to Patch Pending
- Assignee deleted (
- Target version set to 1.4.45
aredridel: Messing with Host request header using mod_setenv is not recommended.
Instead, use proxy.replace-http-host directive in Docs_ModProxy for what it seems like you are trying to do.
Also available in: Atom