我正在编写一个 WebDAV 服务，将由 BitKinex、CyberDuck 和 Windows Explorer 等 WebDAV 客户端使用。我的服务在 BitKinex 和 CyberDuck 等客户端上运行良好，但在 Windows 资源管理器上运行不佳。原因是资源管理器在调用获取文件夹资源时不会将“/”附加到请求 URL。例如。如果它想要一个文件，它会询问
ttp://localhost/davfolder/davfile
但是，当它想要浏览一个文件夹时，它会省略末尾应该存在的“/”
http://localhost/davfolder 而不是 http://localhost/davfolder/
的最后的“/”对于服务器端的某些逻辑是必要的，不能省略。
BitKinex 和 CyberDuck 正确地执行了此操作，因此使用这些客户端没有问题。
我可以通过任何方式设置 Windows 添加尾随“/”，或者我应该说我的服务不支持 Windows 资源管理器。
I am writing a WebDAV service that will be used by WebDAV clients like BitKinex, CyberDuck and Windows Explorer. My service is working well with clients like BitKinex and CyberDuck but is not with Windows Explorer. The reason being explorer doesn't append a '/' to the request url when making a call to get a folder resource. For eg. if it wants a file it will ask
ttp://localhost/davfolder/davfile
however when it wants to browse a folder it omits the '/' that should be there at the end
http://localhost/davfolder instead of http://localhost/davfolder/
The trialing '/' at the end is necessary for some logic on the server side and it can't be omitted.
BitKinex and CyberDuck does this correctly and hence there is no problem using those clients.
Any way I can set windows to add the trailing '/' or should I just say that windows explorer is not supported for my service.
发布评论
评论（2）
Windows 内置的 WebDAV 客户端并不像您期望的那样符合标准。所以你需要找到一个解决方法。总而言之，您在服务器上知道所请求的资源是文件夹还是文件，并且可以采取相应的操作。因此，您需要做的就是检查资源的类型，如果需要，在进一步传递请求之前附加一个斜杠。
Windows built-in WebDAV client is not as standard compliant as you would expect. So you need to find a workaround. All in all, you on the server know whether the requested resource is a folder or a file, and you can act accordingly. So all you need to do is check the type of resource and if needed append a slash before passing the request further.
您的服务必须处理这些请求；我不相信他们不合规。
Your service will have to deal with these requests; I don't believe they are non-compliant.