Skip to content

PROPFIND returns HTTP 500 with empty body for some directories — client reports "response not in XML format #2403

@Cosmekaili-creator

Description

@Cosmekaili-creator

Description:

When syncing a large folder (e.g. a Cryptomator vault) with the Open Cloud desktop client, sync repeatedly fails with:
"Le serveur a renvoyé une erreur lors de la lecture du répertoire « Vault/Shared Vault/d/… » : Erreur du serveur : La réponse PROPFIND n'est pas au format XML !"

OpenCloud version: 5.1.0 (docker image opencloudeu/opencloud-rolling:5.1.0)

Client: Open Cloud desktop (mirall)

Setup: Single user, Basic Auth for WebDAV. Nginx reverse proxy with long timeouts (7200s for /dav/). Container has 3 GB RAM.
Observed in server logs: For the failing PROPFIND requests, Reva returns HTTP 500 with 0 bytes body. The proxy logs "context canceled" and 502. So the client receives no valid WebDAV XML.

Pattern: The failing path changes each run (e.g. Vault/Shared Vault/d/BE, d/B7/…, d/AJ/…). Sync works on the first PC; a second PC syncing the same vault hits these errors repeatedly.

Expected: PROPFIND should either return 207 with valid multistatus XML, or 500 with an error body (not empty).

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    Status

    Qualification

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions