WEBDAV sync error with opencloud

seifi_p · 2026-07-06T10:20:56+00:00

Hi there,

I tried the WEBDAV synchronization with opencloud, an owncloud fork, and get a 425. I use app tokens for authentication and the zotero-test-file is correctly written.
Any help or recommendations are highly appreciated. :)

Debug ID: D1082039904

dstillman · 2026-07-06T15:10:36+00:00

OpenCloud seems to be repurposing an obscure TLS-related HTTP error code for its own application behavior — an uploaded file not yet being available. This seems to break even their own clients.

I'm afraid you'll need to complain to OpenCloud about this or switch to as different server. You may be able to turn off asynchronous file processing. It would be more appropriate for the server to return either a 404 (which Zotero would show an appropriate warning message for, about a file not being available immediately after uploading) or a 503 with Retry-After. We wouldn't add special handling for this because it's a misuse of the status code.

seifi_p · 2026-07-07T08:27:56+00:00

Thanks for looking into this,

I agree with you and would circle this back to opencloud. Can you give me a little more context on what the issue is and how it should be handled?

adamsmith · 2026-07-07T08:36:13+00:00

It's in dstillman's message -- the WebDAV returns the HTTP error code 425 when an uploaded file isn't yet available (I suspect because the literal name of the error code is "too early" and the problem is, in fact, that the attempt to access the file is too early, but that's not actually the scenario the error is meant to communicate). Instead, the server should return one of the two more standard HTTP error codes that dstillman points to.