distribution/registry/client
Milos Gajdos 24de708d22
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>
2023-08-15 08:46:48 +01:00
..
auth Merge pull request #3766 from thaJeztah/gofumpt 2022-11-04 12:19:53 +01:00
transport Support ztsd compression as Content-Encoding 2023-06-01 14:06:25 +01:00
blob_writer.go Set Content-Type header in registry client ReadFrom 2023-08-15 08:46:48 +01:00
blob_writer_test.go use http consts for request methods 2022-11-02 23:31:47 +01:00
errors.go registry/errors: Parse http forbidden as denied 2023-04-27 19:48:32 +02:00
errors_test.go registry/errors: Parse http forbidden as denied 2023-04-27 19:48:32 +02:00
repository.go Merge pull request #3788 from thaJeztah/deprecate_ReadSeekCloser 2022-11-18 08:53:15 +00:00
repository_test.go Ignore SA1019: "schema1 is deprecated" linting errors 2023-05-09 16:04:17 +02:00