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.

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

HTTP Transport compression for Layer downloads #65

Closed
stevvooe opened this issue Jan 14, 2015 · 2 comments
Closed

HTTP Transport compression for Layer downloads #65

stevvooe opened this issue Jan 14, 2015 · 2 comments

Comments

@stevvooe
Copy link
Collaborator

We should add transport layer compression support for the registry server. This should be compliant with RFC7231, Section 5.3.4. This can be implemented as a wrapper around the main application that detects Accept-Encoding headers and acts on the contents.

Supersedes docker-archive/docker-registry#694.

@RichardScothern
Copy link
Contributor

After some research on the subject I don't think this is worth doing. Mainly because tarsum supports - and enables - compression so layers pushed to a repository are already compressed with gzip.

There is also some ambiguity about Content-Range and [non]compressed data. This is probably not a big deal, but will require more than transparently compressing responses.

more discussion here

ping @stevvooe

@dmp42 dmp42 closed this as completed Jul 22, 2015
@stevvooe
Copy link
Collaborator Author

@RichardScothern Agreed. This is unfortunate. We may want to state this somewhere.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants