/SBIN/Mount.davfs:安装失败;该服务器不支持WebDav
我正在尝试安装一个远程WebDav:
sudo Mount -t davfs https://files.isric.org/soilgrids/latest/data/〜/webdav
,但我只会收到以下错误: /sbin/mount.davfs:安装失败;该服务器不支持WebDav
此服务器是 wsgidav 在kubernetes群集中运行。
Nautilus的同样问题,使用 gvfsd-dav
来调试问题,如所示在这里。我有以下服务器的HTTP请求/响应:
/usr/libexec/gvfsd-dav ssl=true user=anonymous host=files.isric.org prefix=/soilgrids/latest/data/
dav: setting 'ssl' to 'true'
dav: setting 'user' to 'anonymous'
dav: setting 'host' to 'files.isric.org'
dav: setting 'prefix' to '/soilgrids/latest/data/'
dav: Added new job source 0x556590e0c1a0 (GVfsBackendDav)
dav: Queued new job 0x556590e0a380 (GVfsJobMount)
dav: + mount
> OPTIONS /soilgrids/latest/data HTTP/1.1
> Soup-Debug-Timestamp: 1657091152
> Soup-Debug: SoupSession 1 (0x556590e0c100), SoupMessage 1 (0x7fa1b40060e0), SoupSocket 1 (0x7fa1b43440e0)
> Host: files.isric.org
> Accept-Encoding: gzip, deflate
> User-Agent: gvfs/1.48.2
> Accept-Language: en-us, en;q=0.9
> Connection: Keep-Alive
< HTTP/1.1 204 No Content
< Soup-Debug-Timestamp: 1657091152
< Soup-Debug: SoupMessage 1 (0x7fa1b40060e0)
< Date: Wed, 06 Jul 2022 07:05:52 GMT
< Connection: keep-alive
< Strict-Transport-Security: max-age=15724800; includeSubDomains
< Access-Control-Allow-Origin: *
< Access-Control-Allow-Credentials: true
< Access-Control-Allow-Methods: GET, OPTIONS, HEAD
< Access-Control-Allow-Headers: Content-Type, Accept-Ranges, Content-Range, Range, Content-Encoding, Content-Length, Access-Control-Allow-Origin
< Access-Control-Max-Age: 1728000
< Content-Length: 0
<
dav: send_reply(0x556590e0a380), failed=1 (Not a WebDAV enabled share)
dav: Mount failed: Not a WebDAV enabled share
服务器HTTP响应是 http/1.1 204没有内容
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
问题在于具有:
http/1.1 204没有内容
响应的K8S入口是正确的前飞行员响应,由提供入口,这是不是预期的WebDav Reponse ,第一个请求甚至没有达到运行WSGIDAV的POD。解决方案:禁用入口上的CORS支持。然后还可以:
The problem lies on the k8s ingress that has:
The
HTTP/1.1 204 No Content
response is the correct pre-flight CORS response that is provided by the ingress, this is not the expected WebDAV reponse, and the first request was not even reaching the pod running wsgidav.Solution: Disable CORS support on ingress. and then things are OK: