Project

Profile

Help

Issue #6814

closed

docker-content-digest header is missing from the response on s3 files

Added by ipanova@redhat.com over 4 years ago. Updated over 4 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Sprint/Milestone:
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 75
Quarter:

Description

we have set content-type and content-disposition headers, but we also need docker-content-digest present among response headers

usecase: Users want to make a HEAD request for a tag to find out if that tag is pointing to a new manifest. Without this header, users must download the manifest in order to learn its digest.

Also available in: Atom PDF