Closed thelazyoxymoron closed 3 months ago
We should probably surface this error to the user.
Did you see DavException: Received redirect from HTTPS to HTTP
? Are you sure you want to use WebDAV over HTTP?
I'm not sure why is that error present in the first place though. I'm using the following setup:
Using docker-nginx-webdav-nononsense behind a reverse-proxy, so there should not be a redirection involved. I don't get this error with other clients.
Can you privately provide a test account or install another instance of that container for testing?
Sure. How do I send the account details?
Documenting the issues I've run into when testing with curl:
curl --user "user:pass" --head 'https://seedvault-backup-test.example.com/.NonExistentFolder'
If you run this in a terminal, you get the redirect to http. So that's something that sounds like a bug in that container? What I would expect here is to get a 404 response, since the folder doesn't exist yet.
curl -H 'Transfer-Encoding: chunked' -H 'Content-Type: image/png' --compressed -v --user "user:pass" -T test.png 'http://seedvault-backup-test.example.com/test.png' -v
Trying to upload a file (test.png
) with curl also gives me 301 redirect
and then doesn't upload.
So either something is wrong with @thelazyoxymoron's reverse proxy or these are strange bugs in the docker-nginx-webdav-nononsense container that we should report to upstream.
Backup fails with the following error:
This is a valid webdav endpoint, works well with Finder network mount on MacOS and other places.