You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Opt-in per-chunk integrity verification on storage proxy uploads.
- Parse \`Upload-Checksum: sha256 <base64-digest>\` on PATCH; compare to
the sha256 computed while streaming the chunk body. On mismatch,
raise \`ChunkChecksumMismatchError\` (HTTP 460 per TUS Checksum
extension) and discard the temp chunk file.
- Reject malformed header values (missing digest, non-sha256 algorithm,
invalid base64, wrong digest length) with
\`InvalidUploadChecksumHeaderError\` (400).
- Advertise the extension in OPTIONS via \`Tus-Extension: checksum\` and
\`Tus-Checksum-Algorithm: sha256\`. Add \`Upload-Checksum\` to the
Access-Control-Allow-Headers / Expose-Headers lists.
Clients that do not send the header observe no behavior change.
Tests cover matching / mismatched / malformed header cases.
Resolves BA-6158. Part of epic BA-6153 (implements BA-3974).
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Support the TUS Checksum extension on storage proxy uploads: clients may now send `Upload-Checksum: sha256 <base64>` and the server rejects mismatched chunks with HTTP 460.
0 commit comments