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

Seafile WebDav sync broken #1137

Closed
thororm opened this Issue Jan 19, 2019 · 2 comments

Comments

Projects
None yet
2 participants
@thororm
Copy link

thororm commented Jan 19, 2019

Operating system

  • Windows
  • Android

Application

  • Desktop
  • Mobile

Hi,

first of all, thank you for this amazing piece of software.

Unfortunately, the fix for the nginx WebDav sync, that was made with this commit:
3943192
breaks the syncing with a seafile WebDav server.
I was able to use the debugging to see, that the exception is thrown at that location.

The issue is already reproducible with the "Check synchronisation configuration"

The response from seafile looks like this:

<?xml version="1.0" encoding="UTF-8"?>
<ns0:multistatus xmlns:ns0="DAV:">
   <ns0:response>
      <ns0:href>/seafdav/joplin/</ns0:href>
      <ns0:propstat>
         <ns0:prop>
            <ns0:getlastmodified />
         </ns0:prop>
         <ns0:status>HTTP/1.1 404 Not Found</ns0:status>
      </ns0:propstat>
      <ns0:propstat>
         <ns0:prop>
            <ns0:resourcetype>
               <ns0:collection />
            </ns0:resourcetype>
         </ns0:prop>
         <ns0:status>HTTP/1.1 200 OK</ns0:status>
      </ns0:propstat>
   </ns0:response>
</ns0:multistatus>

I also tested it with a previous version (v1.0.117) where the sync is still working.

@laurent22

This comment has been minimized.

Copy link
Owner

laurent22 commented Jan 20, 2019

Could you create a test user on your server and send the info to this address?

Also does the path /seafdav/joplin/ exists? Because if it does it's strange the server would return 404?

@thororm

This comment has been minimized.

Copy link
Author

thororm commented Jan 20, 2019

I've sent you the access data with a test account.

Yes, the directory does exist, I can access it and also transfer files with other WebDav clients
I don't know WebDav, but to me it seems like the 404 is only for the getlastmodified?

@laurent22 laurent22 closed this in 53166cb Jan 25, 2019

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