Repository navigation
0.3.12
Fixed: every export failure returned 409.
exists, unsupported, empty, unwritable and unreadable all came back as 409, so the settings row could not tell "press confirm to overwrite" from "retrying will never help". A read-only path or a Node without getCACertificates kept the row offering a confirmation that could never succeed.
Now: exists → 409, unsupported/empty → 422, everything else → 500. The row only enters its confirm state on 409, and shows 422/500 as a plain failure.
Fixed: a malformed request body was silently read as force: false. A caller sending broken JSON got reason: exists and would conclude the export was impossible, when the real problem was its own request. It now answers 400 with bad-request.
The body reader also destroys the request past its 8 KB cap instead of leaving the stream open.
Gates: offline 104 (2 new), client 27, packaging 20, release 34.
Full Changelog: v0.3.11...v0.3.12