On Tue, 30 Sep 2008 09:50:00 -0400 "Tom Wells" <[EMAIL PROTECTED]> wrote:
> ServerName munchkin.synthesis.co.za > Header add Set-Cookie "MOD_PROXY_FOOD=FOO;" early Why? The "early" keyword exists to help developers simulate a request, for example when debugging a new module. Perhaps it should've remained undocumented. > Also (as far as I understand) modproxy > should try to preserve any headers already set before processing by > merging the headers before and after processing (especially any > Set-Cookie headers). HTTP has no provision for a proxy to set an end-to-end header such as Set-Cookie - only how it should deal with headers set by the backend. mod_headers isn't part of the protocol implementation; it's a convenience for users who want to change the default behaviour. > Maybe this is normal modproxy behaviour, I can't be certain, but > reading through some of mod_proxy_http.c seems to show that this is > the intention. However I was able to test this on another Apache > instance running 2.2.4 and modproxy retains both cookies in both > cases. So either this is a bug in 2.2.9 or it's a bug that was fixed > since 2.2.4. It's probably a side-effect of fixing https://issues.apache.org/bugzilla/show_bug.cgi?id=16518 and associated improvements. But it's not a bug now, nor was it before. If you want to set a header with predictable behaviour, don't use "early". -- Nick Kew Application Development with Apache - the Apache Modules Book http://www.apachetutor.org/ --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
