https://bz.apache.org/bugzilla/show_bug.cgi?id=65823
Dr. Rolf Jansen <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Resolution|--- |INVALID --- Comment #2 from Dr. Rolf Jansen <[email protected]> --- I adjusted the loglevel of the Apache proxy and I ran my WebDAV service in diagnostic mode which logs all the http request/response headers. With that it became evident, that the trailing slashes became already removed by the Windows WebDAV client (Microsoft-WebDAV-MiniRedir/10.0.19043). In this case my WebDAV service responds with a 301, giving back the URI with the trailing slash in the Location: field. Now for some reasons which only Microsoft knows, the WebDAV client does the correct thing when the Location:-URI is not on the standard port, but on 13939 - that is in this case it tries again with the trailing slash. In case the ProxyPass port is left to 80, the MS WebDAV client stops working after receiving the 301 and bails out — network error. I also have no idea on why this setup worked right at the end of last year, and now it does not anymore. Anyway, when looking closer on this behaviour, I am confident, that there is nothing wrong with Apache and its proxy modules. My failure, and please excuse the false alarm. From my point of view, this issue can be closed. I did build now my WebDAV service with the directive NOREDIR_FIXSLASH, which lets the service fix missing slashes and by this does not send a 301 to the client. This is not ideal, but it is obviously necessary for Microsofts WebDAV. Sorry again for the inonvenience. Best regards Rolf Jansen -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
