httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 38550] - Setting headers based on proxied data
Date Wed, 08 Feb 2006 16:36:08 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38550>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=38550





------- Additional Comments From apache@rikrose.net  2006-02-08 17:36 -------
mod_headers is indeed the correct place to do so, but it's also a far more
difficult place to do so, because mod_headers can not read an existing value to
assign it elsewhere - it can only assign values from the config file. In order
to (want to) use mod_headers the code to read existing headers and cookies to
use as values, like mod_rewrite's %{HTTP_foo} etc would need to be added.

The easiest way to think about what I'm doing is that I'm setting a cookie for
the browser after an application that acts as a cookie jar - think sneaking a
cookie past an anonymising proxy, by disguising it in a header, and rewriting it
back.

I agree, in principal, mod_rewrite is a completely stupid place to do this hack.
On the other hand, it's a very very easy place to do it, as all of the support
code is in place.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message