> -----Ursprüngliche Nachricht----- > Von: Sander Temme > Gesendet: Mittwoch, 9. Januar 2008 08:01 > An: [email protected] > Betreff: Re: mod_dav patch to force scheme/port on > https->http proxying > > > > On Jan 8, 2008, at 3:10 PM, David Sklar wrote: > > > Any comments on the patch would be appreciated -- it's > wonderful, it's > > a good solution but could be improved, it's a ridiculous > way to solve > > this problem, etc. > > Doesn't setting the global directive: > > ServerName https://foo.bar:443 > > already do what you need? > > I'd rather see a solution in terms of that directive (where mod_dav > picks up the setting in core which is there specifically for the > scenario you describe and is available through the > ap_hook_http_scheme > hook), or an extension to the ProxyPassReverse case which rewrites > this particular repsonse part in addition to any Location: header it > encounters.
I agree that a general solution is preferred. Changing headers like the Location header of incoming requests is already possible via mod_headers, but what makes things really nasty with WebDAV is the fact that you also need to modify the body of the request. For responses you could use mod_substitute to do this, but mod_substitute is only an output filter not an input filter. Regards Rüdiger
