Has anyone gotten OmniPresence working with webdav backed by nginx?
I’ve been in the process of trying to slim down my server environment, and I think I can entirely eliminate running Apache by using nginx + webdav.
The webdav server itself works – I can connect with other clients and add/delete/move data. OmniPresence is able to connect as well. It fails on this test:
/webdav/OmniDAV-Conformance-Tests-ht5tX4zoQgC/fortestReplacedCollectionUpdatesModificationDate:-/parent/tmp/doc" could not be MOVEed to collection “https:///webdav/OmniDAV-Conformance-Tests-ht5tX4zoQgC/fortestReplacedCollectionUpdatesModificationDate:-/parent/doc”
Doing some research, this seems like it could be related to this similar Owncloud issue, maybe around etags on a collection?
(I tried to build the OmniFrameworks and run those tests but couldn’t get them to build.)
The only difference I can see in those two requests is the ‘-’ character rather than the escaped space (%20). I don’t know why that would trip it up. I had thought it was the Overwrite header, but I’m not sure if it is now or not.
I don’t think the same solution works. I already had those settings (from your blog post) enabled on my account, using nginx-full (vs nginx-extras) and I’m getting the same errors when retrying now.
The error it eventually fails on during the test is the same as I mentioned above.
It’s unclear to me if it’s the same fix necessary from the OmniFocus changes, or if the webdav needs of OmniPresence are more complex than OmniFocus. It may be the latter, as the test suite for the OmniPresence framework go into complicated overwrite situations.