Koofr WebDAV – repeated HTTP 423 errors on PUT requests after timeout (Zotero 9.0.6)
Hi,
I am having persistent WebDAV synchronization issues between **Zotero 9.0.6 (64-bit) on Windows 11** and **Koofr WebDAV**.
My WebDAV configuration is:
`https://app.koofr.net/dav/Koofr`
I authenticate using my Koofr account email and an application-specific password.
### Problem
Zotero repeatedly receives **HTTP 423 Locked** errors when uploading attachment ZIP files through WebDAV.
The errors occur during **PUT requests**, for example:
`/dav/Koofr/zotero/HV5XATVT.zip`
`/dav/Koofr/zotero/J35KR9Y5.zip`
`/dav/Koofr/zotero/WJL9FFTY.zip`
`/dav/Koofr/zotero/BED3KRK2.zip`
`/dav/Koofr/zotero/2URZE23Y.zip`
`/dav/Koofr/zotero/CRLL656S.zip`
So this does not appear to be limited to one specific attachment.
The Zotero log repeatedly contains messages such as:
`Upload request 1/J35KR9Y5 failed`
followed by:
`Your WebDAV server returned an HTTP 423 error for a PUT request`
### What I tried
I initially received repeated HTTP 423 errors.
I then:
1. Switched file synchronization temporarily from WebDAV to **Zotero Storage**.
2. Ran a synchronization.
3. Switched file synchronization back to **Koofr WebDAV**.
After doing this, WebDAV synchronization started working again temporarily.
However, shortly afterwards Zotero displayed:
`Request timed out after 30000 ms`
After that timeout, the HTTP 423 errors started occurring again on multiple PUT requests.
I have also:
* regenerated the Koofr application password;
* checked the WebDAV URL;
* restarted Zotero;
* stopped repeatedly using the “Verify Server” function;
* disabled automatic synchronization for now.
### Koofr support response
I contacted Koofr support and explained the problem. Their response was:
> “423 error means that one of your applications locked a file and hasn’t properly released the lock. Please contact your application developers.”
They referred me to their WebDAV documentation about HTTP 423 errors.
However, from previous Zotero forum discussions, I understand that **Zotero does not normally use WebDAV LOCK/UNLOCK requests**.
This is therefore where I am confused.
Could someone from the Zotero team help me determine:
* whether Zotero 9.0.6 could be creating or triggering these locks in some other way;
* whether the 30-second timeout immediately preceding the new 423 errors could be relevant;
* whether there is anything in Zotero's WebDAV implementation that could leave Koofr considering a partially uploaded resource “locked”;
* and what information/logging I should send to Koofr to help them investigate this server-side?
I provide a full Debug ID : D1820154356 reproducing the issue.
For now I have disabled automatic synchronization but have not reset file sync history or modified my Zotero database.
Thank you!
I am having persistent WebDAV synchronization issues between **Zotero 9.0.6 (64-bit) on Windows 11** and **Koofr WebDAV**.
My WebDAV configuration is:
`https://app.koofr.net/dav/Koofr`
I authenticate using my Koofr account email and an application-specific password.
### Problem
Zotero repeatedly receives **HTTP 423 Locked** errors when uploading attachment ZIP files through WebDAV.
The errors occur during **PUT requests**, for example:
`/dav/Koofr/zotero/HV5XATVT.zip`
`/dav/Koofr/zotero/J35KR9Y5.zip`
`/dav/Koofr/zotero/WJL9FFTY.zip`
`/dav/Koofr/zotero/BED3KRK2.zip`
`/dav/Koofr/zotero/2URZE23Y.zip`
`/dav/Koofr/zotero/CRLL656S.zip`
So this does not appear to be limited to one specific attachment.
The Zotero log repeatedly contains messages such as:
`Upload request 1/J35KR9Y5 failed`
followed by:
`Your WebDAV server returned an HTTP 423 error for a PUT request`
### What I tried
I initially received repeated HTTP 423 errors.
I then:
1. Switched file synchronization temporarily from WebDAV to **Zotero Storage**.
2. Ran a synchronization.
3. Switched file synchronization back to **Koofr WebDAV**.
After doing this, WebDAV synchronization started working again temporarily.
However, shortly afterwards Zotero displayed:
`Request timed out after 30000 ms`
After that timeout, the HTTP 423 errors started occurring again on multiple PUT requests.
I have also:
* regenerated the Koofr application password;
* checked the WebDAV URL;
* restarted Zotero;
* stopped repeatedly using the “Verify Server” function;
* disabled automatic synchronization for now.
### Koofr support response
I contacted Koofr support and explained the problem. Their response was:
> “423 error means that one of your applications locked a file and hasn’t properly released the lock. Please contact your application developers.”
They referred me to their WebDAV documentation about HTTP 423 errors.
However, from previous Zotero forum discussions, I understand that **Zotero does not normally use WebDAV LOCK/UNLOCK requests**.
This is therefore where I am confused.
Could someone from the Zotero team help me determine:
* whether Zotero 9.0.6 could be creating or triggering these locks in some other way;
* whether the 30-second timeout immediately preceding the new 423 errors could be relevant;
* whether there is anything in Zotero's WebDAV implementation that could leave Koofr considering a partially uploaded resource “locked”;
* and what information/logging I should send to Koofr to help them investigate this server-side?
I provide a full Debug ID : D1820154356 reproducing the issue.
For now I have disabled automatic synchronization but have not reset file sync history or modified my Zotero database.
Thank you!
Upgrade Storage
switching file sync from Koofr WebDAV to Zotero Storage,
completing a sync,
switching back to Koofr WebDAV,
triggering a normal sync.
The HTTP 423 errors occurred again immediately.
Debug ID for the failed synchronization: D1820154356
Koofr support says that HTTP 423 means the client locked the files and did not release the locks, and they referred me back to Zotero.
Could you please check the debug output and tell me whether Zotero is sending any LOCK request, or what exactly happens immediately before Koofr returns HTTP 423?
Several different attachment ZIP files are affected, so this is not limited to one item.