Issue #8543
closedRange headers during blob upload should be inclusive
Description
Docker push of the same tag results in 2 different manifests. This happens because of the Range header not being inclusive on the blob upload response.
Before creating and sending manifest to the server, docker client asks the server whether blobs are being present by looking at the Range header issued by a PATCH requests during upload.
https://github.com/distribution/distribution/blob/6affafd1f030087d88f88841bf66a8abe2bf4d24/registry/client/blob_writer.go#L68 https://github.com/distribution/distribution/blob/6affafd1f030087d88f88841bf66a8abe2bf4d24/registry/handlers/blobupload.go#L321-L324
Updated by ipanova@redhat.com over 3 years ago
- Assignee set to ipanova@redhat.com
- Sprint set to Sprint 94
Updated by pulpbot over 3 years ago
- Status changed from NEW to POST
Added by ipanova@redhat.com over 3 years ago
Added by ipanova@redhat.com over 3 years ago
Revision 79478784 | View on GitHub
Updated Range header in the blob upload response so it is inclusive.
closes #8543
Updated by ipanova@redhat.com over 3 years ago
- Status changed from POST to MODIFIED
Applied in changeset 79478784757fcf0e64f64bbc714063c06ad7b64d.
Updated by pulpbot over 3 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Updated Range header in the blob upload response so it is inclusive.
closes #8543