Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Proposal: Add content-encoding support to spec for reading blobs #301

Open
sargun opened this issue Oct 1, 2021 · 1 comment
Open

Proposal: Add content-encoding support to spec for reading blobs #301

sargun opened this issue Oct 1, 2021 · 1 comment

Comments

@sargun
Copy link
Contributor

sargun commented Oct 1, 2021

Following up on #235, I believe we should require that content-encoding is supported for fetching blobs. All registries today could treat this effectively as a "no op" upgrade, and encode everything with the "identity" encoding.
@vbatts
Copy link
Member

vbatts commented Oct 21, 2021

+1 to working with uncompressed blobs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@vbatts @sargun