Closed tuaris closed 4 years ago
Just for fun I setup a simple WebDAV server using Apache
<VirtualHost *:80>
DocumentRoot /var/ftp/incoming/WebDAV
ServerName webdav.my.domain
DAVMinTimeout 600
DAVLockDB /var/spool/webdav/DAVLock
<Location />
DAV on
</Location>
</VirtualHost>
The result is the same but the error is slightly different:
[error] WebDAV failed to connect: t.multistatus.response.filter is not a function
I can confirm that WebDAV is working using WinSCP as a client to upload and download files. (for both this test server and Owncloud)
Hmm, I don't get any failures on Chrome/Firefox for webdav vaults - either adding new or unlocking anold one. Mind you I'm not testing on Nextcloud at the moment. I'll try on Nextcloud next.
I can't even seem to get authenticated with Nextcloud:
I'm testing on Yandex's WebDAV which works fine. My OwnCloud as well. I won't rule out that there's some bug in the webdav handling, but I suspect that there's some other issue going on with the response you're seeing in both of your cases.
t.multistatus.response.filter
seems like the WebDAV response you got was invalid or of a structure that I'm not familiar with (as I'm the author of the webdav library we're using). If you could share any of your PROPFIND responses, that might help.
I get also a connection error with my owncloud, but the error messages are different: #336
@tuaris Still seeing this issue?
I'm going to close this issue, for now - We don't openly support Nextcloud or ownCloud, as they're (by default) configured incorrectly for "true" WebDAV access (in that it has CORS issues when accessed from the web via Buttercup scripts). There's no way around this from our side, and requires that either ownCloud fix the issue (and Nextcloud downstream), or that the server owner implements a hack (as I've done on my ownCloud).
Due to this, I'll close this as WebDAV works fine with services that provide a valid WebDAV interface (Yandex). If we see this more broadly, I'll happily reopen.
Using extension version 2.14.0.
I'm aware of #282 and #174 but neither of those appear to be the issue I'm observing. I've tested this with my own personal Owncloud instance and the one over at demo.nextcloud.com. From my understanding, both Owncloud and Nextcloud use https://sabre.io/ for webdav implementation.
To reproduce:
Here's what the Firefox console shows:
This is the response payload from the server
On the server side the logs show (obviously from my personal instance):