Issue #8543: Range headers during blob upload should be inclusive - Container Support - Pulp

Actions

Send by e-mail Copy link

Issue #8543

closed

Range headers during blob upload should be inclusive

Added by ipanova@redhat.com about 3 years ago. Updated almost 3 years ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

Normal

Assignee:

ipanova@redhat.com

Sprint/Milestone:

2.6.0

Start date:

Due date:

Estimated time:

Severity:

2. Medium

Platform Release:

OS:

Triaged:

Groomed:

Sprint Candidate:

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