You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2007/03/01 06:51:41 UTC

DO NOT REPLY [Bug 41698] - Site documentation of Header edit is missing

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=41698>.
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=41698





------- Additional Comments From rea-asf@codelabs.ru  2007-02-28 21:51 -------
Ruediger,
(In reply to comment #8)
> (In reply to comment #5)
> > Could you please give the Apache configuration exempt for which my patch will
> > break mod_rewrite: I will try to see if it can be fixed.
> 
> It does not break mod_rewrite, but it does not work with mod_rewrite, as after
> applying your patch things will behave differently when you do proxying via
> ProxyPass or mod_rewrite
> 
> To give you a simple example:
> 
> RewriteRule ^/(.*) http://backend.org/$1 [P]
> 
> does the same as
> 
> ProxyPass / http://backend.org/
> 
> But using the RewriteRule instead of ProxyPass will leave the Destination header
> unchanged with your patch. The basic shortcoming of your patch is that it does
> not apply all the transformations done to the original request URL to the
> Destination header URL, so they get out of sync. You only apply the
> transformations caused by ProxyPass. Most of these transformations are done
> during the translate_name hook, but some of them are also done during the fixup
> phase (mod_rewrite in directory context).

OK, if I will enable mod_rewrite to do the same Destination rewriting and will
apply 'all the transformations done to the original request URL' -- will it have
a chance to be committed? To tell the truth, just now I have no idea what are
those 'all transformations' but will try to understand. May be you will be so
kind to point me to the relevant code locations?

And if we will turn this into the documentation issue, I will vote that
mod_dav's documentation should note that the 'Destination' should be rewritten
if we're living with the proxy. It is not obvious for the administrator when the
proxied DAV is refusing to to PUT and MOVE.


-- 
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