You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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.
The text was updated successfully, but these errors were encountered: