distribution/registry/client
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
..
auth Fix gosimple checks 2021-03-23 21:03:20 +08:00
transport Revert "registry/client: set Accept: identity header when getting layers" 2023-05-10 23:00:15 +02:00
blob_writer.go Set Content-Type header in registry client ReadFrom 2023-09-08 14:45:13 +02:00
blob_writer_test.go Fix gosimple checks 2021-03-23 21:03:20 +08:00
errors.go registry/errors: Parse http forbidden as denied 2023-05-11 10:45:46 +02:00
errors_test.go registry/errors: Parse http forbidden as denied 2023-05-11 10:45:46 +02:00
repository.go bump up golang version 2023-05-09 10:59:43 +02:00
repository_test.go Fix gosimple checks 2021-03-23 21:03:20 +08:00