Project

Profile

Help

Issue #8543

Range headers during blob upload should be inclusive

Added by ipanova@redhat.com about 1 month ago. Updated 24 days ago.

Status:
MODIFIED
Priority:
Normal
Sprint/Milestone:
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
GalaxyNG
Sprint:
Sprint 94
Quarter:

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

Associated revisions

Revision 79478784 View on GitHub
Added by ipanova@redhat.com about 1 month ago

Updated Range header in the blob upload response so it is inclusive.

closes #8543

Revision 79478784 View on GitHub
Added by ipanova@redhat.com about 1 month ago

Updated Range header in the blob upload response so it is inclusive.

closes #8543

History

#1 Updated by ipanova@redhat.com about 1 month ago

  • Assignee set to ipanova@redhat.com
  • Sprint set to Sprint 94

#2 Updated by pulpbot about 1 month ago

  • Status changed from NEW to POST

#3 Updated by ipanova@redhat.com about 1 month ago

  • Status changed from POST to MODIFIED

#4 Updated by ipanova@redhat.com 24 days ago

  • Sprint/Milestone set to 2.6.0

Please register to edit this issue

Also available in: Atom PDF