distribution/registry
Milos Gajdos cb121c3f20
Set Content-Type header in registry client ReadFrom
Client ReadFrom doesn't set Content-Type header leading to server
side implementor to assume it's application/octet-stream. This commit
makes this explicit on the client side.

Signed-off-by: Milos Gajdos <milosthegajdos@gmail.com>
(cherry picked from commit 24de708d22)
Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
2023-09-08 14:45:13 +02:00
..
api Fix runaway allocation on /v2/_catalog 2023-04-24 18:53:43 +02:00
auth Fix gofmt warnings 2023-05-09 18:58:38 +01:00
client Set Content-Type header in registry client ReadFrom 2023-09-08 14:45:13 +02:00
handlers Merge pull request from GHSA-hqxw-f8mx-cpmw 2023-05-09 21:21:54 +01:00
listener [Server] Listen and serve on a unix socket 2015-05-11 16:00:14 +03:00
middleware context: remove definition of Context 2017-08-11 15:53:31 -07:00
proxy Fix gometalint errors 2021-03-23 21:03:10 +08:00
storage Enable build tags in 2.8 2023-08-21 13:58:10 +02:00
doc.go Move initialization code from main.go to the registry package 2015-09-09 14:39:31 -07:00
registry.go Merge pull request #3384 from wy65701436/release/2.7-cp-3169 2021-03-23 15:23:04 +00:00
registry_test.go Added flag for user configurable cipher suites 2021-03-23 18:42:12 +08:00
root.go add possibility to clean untagged manifests 2018-01-05 12:20:01 +02:00