Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Android WebDAV Error: 412 Unknown error #1228

Closed
temaoz opened this issue Feb 16, 2019 · 2 comments

Comments

@temaoz
Copy link

commented Feb 16, 2019

Operating system

  • Android

Application

  • Mobile

Currently it isn't possible to enable the WebDAV sync between Joplin and mailbox.org (which uses OpenXchange).

The WebDAV URL and credentials are correct. WebDAV Sync in general is working without any problemsn and e.g. used with Kepass2Android for syncing the database file.

When I enter the WebDAV URL and the credentials in Joplin and click the button to check the settings, I get the following error:

'PROFIND: Unknown error 2 (412): (Code 412)

You can test the WebDAV sync with the following credentials and URL:

URL: https://dav.mailbox.org/servlet/webdav.infostore/Userstore/Joplin%20Testuser/Documents/Joplin
User: joplin_test@mailbox.org
Password: J0plin19!

I've also attached my error log below.

syncReport-1550322713286.txt

@danieldev

This comment has been minimized.

Copy link

commented Feb 22, 2019

I can reproduce this bug. There is already an issue for that which was closed even though this problem still occurs with mailbox.org: #1064

@laurent22

This comment has been minimized.

Copy link
Owner

commented Feb 23, 2019

This is a bug in their WebDAV implementation so it needs to be reported either to mailbox.org or OpenXchange.

For various reasons described there, Joplin sends a random "If-None-Match" header with PROPFIND call. A non-buggy implementation like Nextcloud would look at this header, see that it doesn't correspond to any resource (it's a cache miss), and thus send back what was requested.

However OpenXchange seems to look at this tag, see that there's no such resource and respond with an error. According to RFC-7232, it shouldn't because it's just a cache miss - it should just send back the requested resource.

I cannot be fixed easily in Joplin (if we fix it for OpenXchange we'll break other things) so for that reason it won't be fixed here.

@laurent22 laurent22 closed this Feb 23, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.