On Apr 17, 2008, at 10:04 AM, Plüm, Rüdiger, VF-Group wrote:
But sure this could be also fixed in the appropriate canon_handler hooks of mod_proxy_http and mod_proxy_ajp.
That's what I'm wondering... Treating this "special" inside of mod_proxy itself, when it's really a protocol issue (and what is "right" for that protocol) just seems a safer way. Or, at least, helps to maintain that illusion of abstraction :)
