>Number:         4304
>Category:       mod_headers
>Synopsis:       It'd be useful to be able to alter request headers as well as 
>response ones.
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          change-request
>Submitter-Id:   apache
>Arrival-Date:   Sat Apr 24 07:30:00 PDT 1999
>Last-Modified:
>Originator:     [EMAIL PROTECTED]
>Organization:
apache
>Release:        1.3.4
>Environment:
Debian 2.1 (Linux 2.0.36)
>Description:
At the moment mod_headers manipulates response headers. It would be useful
to be able to manipulate request headers. You can then customise the request
before it is passed on by mod_proxy. In my case I'm using apache to 
transparently
hide several (less flexible) web servers behind it, and want apache to handle
the authorisation of the client and then remove the Authorization header from
the request before it is passed on. I can also see cases for adding headers
to the request to pass information to the hidden server.
>How-To-Repeat:

>Fix:
I've done a fairly simple patch to add a "HeaderRequest" configuration command
which is the same as the "Header" command, except it affects request headers
instead of response headers. The patch is available at:
http://marvin.nipltd.com/~matt/mod_headers.patch
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <[EMAIL PROTECTED]> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.                                      ]
[Reply only with text; DO NOT SEND ATTACHMENTS!         ]



Reply via email to