Talk:Foxmarks: Error: Unknown error 0x19C
From Foxcloud Wiki
I don't knov for sure when this error appeared. But I saw it for the first time the day after updating to 0.41.
I noticed that firefox failed to get the new bookmarks from another computer and tried a manual synchronization which failed with this message.
I'm using my own webdav server and everything has been working fine until now.
- Indeed, in version .41 we added code to prevent a potential overwrite condition, where another client changes the server file that a Foxmarks client was about to modify. Since Foxmarks hasn't incorporated changes from the new file, those changes would be lost if Foxmarks were to proceed; the error causes it abort the synchronization.
- If you are running Foxmarks on multiple machines and you get this error, it's a normal (though unlikely) behavior. If you get it constantly, something is wrong, most likely with you webdav server's support of etags. See http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html section 14.24 for details. --Todd 14:46, 10 January 2006 (EST)
- The error keeps on coming.
- I'm using apache 2.0.54. Having a look through the docs i found the FileETag Directive
- The only setting that would allow Foxmarks to work was: FileETag None
- I have some difficulty believing that this is the setting I should be using. Doesn't this basically disable the check you perform by always responding with the same value?
- To be perfectly honest I'm somewhat sceptical as to this being a problem with apache rather than FoxMarks ;) The one is a very stable mature product, the other in beta and the misbehaving feature was introduced in the latest version...
- Seems my scepticism was most likely unfounded. A search through apache bugzilla found this: PUT/If-match (etag) handling seems to be broken
- Thanks for taking the time to track this down, and thanks also for enhancing the wiki with your findings.
- We're all in favor of a healthy skepticism. But we're also glad that this time it was somebody else's bug (for once!). Happy syncing. --Todd 10:40, 11 January 2006 (EST)
- Seems my scepticism was most likely unfounded. A search through apache bugzilla found this: PUT/If-match (etag) handling seems to be broken

