Cordy/Cairn
2
1
Fork 0
Code Issues 15 Pull requests Projects Releases Packages Wiki Activity Actions

Quota enforcement (507 on write) #14

New issue
Closed
opened 2026-07-25 16:25:18 +00:00 by Cordy · 1 comment
Cordy commented 2026-07-25 16:25:18 +00:00
Owner
Copy link

Reporting already ships (GET /api/v1/quota + WebDAV RFC 4331 props, v0.2.1). This is the enforcement half: reject writes that would exceed a configured cap.

  • Global and/or per-user cap (config).
  • Enforce on REST upload, WebDAV PUT, and TUS finalize; return 507 Insufficient Storage (WebDAV) / appropriate JSON error (REST).
  • Feature-detected via storage.Usager; POSIX via statfs, S3 has no bucket-wide capacity so per-user accounting is the realistic path there.

Last remaining functional item in v0.3.

Reporting already ships (`GET /api/v1/quota` + WebDAV RFC 4331 props, v0.2.1). This is the *enforcement* half: reject writes that would exceed a configured cap. - Global and/or per-user cap (config). - Enforce on REST upload, WebDAV PUT, and TUS finalize; return `507 Insufficient Storage` (WebDAV) / appropriate JSON error (REST). - Feature-detected via `storage.Usager`; POSIX via statfs, S3 has no bucket-wide capacity so per-user accounting is the realistic path there. Last remaining functional item in v0.3.
Cordy commented 2026-07-26 14:55:35 +00:00
Author
Owner
Copy link

Shipped in v0.2.5 (PR #34): storage.quota decorator at the write chokepoint — maxFileBytes (any backend, enforced mid-stream), maxTotalBytes/reserveBytes (Usager-backed), storage.ErrQuotaExceeded → 507 on WebDAV, JSON error on REST/TUS. Issue was left open by mistake; closing retroactively.

Shipped in **v0.2.5** (PR #34): `storage.quota` decorator at the write chokepoint — `maxFileBytes` (any backend, enforced mid-stream), `maxTotalBytes`/`reserveBytes` (Usager-backed), `storage.ErrQuotaExceeded` → 507 on WebDAV, JSON error on REST/TUS. Issue was left open by mistake; closing retroactively.
Cordy closed this issue 2026-07-26 14:55:35 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
v0.3.3
v0.3.2
v0.3.1
v0.3.0
v0.2.7
v0.2.6
v0.2.5
v0.2.4
v0.2.3
v0.2.2
v0.2.1
v0.2.0
v0.0.3
v0.0.2
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
v0.3 — Sovereignty complete
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Cordy/Cairn#14
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?