AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
17:24:47,381 INFO ch. - Accept-Encoding: gzip,deflate 17:24:47,381 INFO ch. - Cookie: _Host-nc_sameSiteCookielax=true _Host-nc_sameSiteCookiestrict=true oc_sessionPassphrase=*** The transcript for a GET request: 17:24:47,380 INFO ch. - GET /remote.php/dav/files/myuser/myfile.docx HTTP/1.1 Files always have the long format.Ĭan you confirm that the short format can also exist for files or is there a chance that the server confuses with the etags? etag from the GET request: 652419851b3daįrom my experience (didn’t check the code) the shorter format 65.last etag the client saw for that file: 6d0ba3cc9cfbdbb9c96de019fd618de9.What confuses me is the different format of the etag for that file: Looking at the log file I see that the etag we get from the server is different from the one we saw the last time we indexed the file which indicates a change/conflict. We now have a customer reporting a sync conflict which should not happen as the file was not touched from anyone else (he says). Our webdav based sync client uses etags to detect changes/conflicts. Feel free to move the topic to a more appropriate category.
0 Comments
Read More
Leave a Reply. |