-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
MacOS desktop client can't connect to WebDAV #2040
Comments
This may be related to #1755 as when I hit the URL in my browser I get a directory listing |
Looks like a known issue with this container: BytemarkHosting/docker-webdav#4 Going to close this |
Actually @laurent22 any thoughts on why this is not an issue for the iOS client? |
I have no idea, as this is the same code for iOS and all the other clients. I know that iOS adds extra headers which was causing bugs and for which I had to add workarounds, so it's possible these extra headers are actually making it work in this particular case. |
Got it. Well for what it's worth, I checked the Docker logs for my container and it looks like both the iOS client and MacOS client get 405's when making the MKCOL call, but the MacOS client performs multiple PROPFINDs which each return a 301 while the iOS client performs a single PROPFIND which returns a 207. I wonder if the 207 is encapsulating the multiple 301s but it's being treated as an OK here: https://github.com/laurent22/joplin/blob/master/ReactNativeClient/lib/WebDavApi.js#L405. If that's the case, the question is what are the implications of ignoring those errors and continuing with the sync operations? |
I've reopened this just to ensure visibility for this conversation. If there's nothing to be done here I am fine with closing it again as it appears the real problem is in my Apache implementation and not Joplin per se, it's just the inconsistency between clients that's still bugging me 😄 |
That's why these kind of issues belong to the forum. Whatever the outcome, people will see the discussion. And let's be honest. No user searches closed tickets (they don't even ssearch open ones). And we can't leave it open either, because otherwise we'd have an unmanageable number of issues. @laurent22 maybe we could add another label that indicates some useful info, so at least we can create a link that lists those issues for reference. |
When attempting to synchronize to my WebDAV server using the desktop MacOS client, I get the following error:
Error: PROPFIND .lock: Cannot parse XML response (200)
. As you can see in the logs below, Joplin seems to be going somewhere unexpected because it is seeing responses from the NAS that my WebDAV server is being hosted on rather than the WebDAV server itself. Three things of note:Environment
Joplin version: 1.0.170
Platform: Synology Docker bytemark/webdav:latest
OS specifics: MacOS Catalina (10.15)
Steps To Reproduce
Describe what you expected to happen: Synchronization is successful
Logfile
The text was updated successfully, but these errors were encountered: