https://bz.apache.org/bugzilla/show_bug.cgi?id=65823
--- Comment #4 from Dr. Rolf Jansen <apa...@cyclaero.com> --- Please may I ask a question? I was under the assumption that the proxy module corrects the Location: response header field. Is that assumption correct? -- I still feel a little bit uncomfortable to let my WebDAV server fix the missing slashes instead of sending a 301 - since I am not sure about all possible implications (some of which may be security related). So at the last weekend, I ran some more tests. And when I let my server check for the presence of the X-Forwarded-Host request header field and based on this let it correct the Location: field of the 301 response, then the Windows WebDAV client did work without a problem. I am talking about the client of the base system (latest Windows 10), which can be used to map network shares. Another observation which makes everything much more strange is that the Windows WebDAV client worked, when running my WebDAV server on the port 13939. That means in this case Windows happily did the correct thing when receiving the 301 with the local non-proxied URI with slash, like Location: http://10.11.0.1:13939/rolf/ On the other hand, when my WebDAV server runs on port 80, then the 301 response is Location: http://10.11.0.1/rolf/ and Windows WebDAV stops working after receiving this one. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org For additional commands, e-mail: bugs-h...@httpd.apache.org
