-
- Downloads
registry: fix binary JSON content-type
This fixes registry endpoints to return the proper `application/json` content-type for JSON content, also updating spec examples for that. As per IETF specification and IANA registry [0], the `application/json` type is a binary media, so the content-type label does not need any text-charset selector. Additionally, the media type definition explicitly states that it has no required nor optional parameters, which makes the current registry headers non-compliant. [0]: https://www.iana.org/assignments/media-types/application/json Signed-off-by:Luca Bruno <lucab@debian.org>
Showing
- contrib/compose/README.md 1 addition, 1 deletioncontrib/compose/README.md
- docs/spec/api.md 91 additions, 91 deletionsdocs/spec/api.md
- docs/spec/auth/token.md 1 addition, 1 deletiondocs/spec/auth/token.md
- health/health.go 1 addition, 1 deletionhealth/health.go
- registry/api/errcode/handler.go 1 addition, 1 deletionregistry/api/errcode/handler.go
- registry/api/v2/descriptors.go 29 additions, 29 deletionsregistry/api/v2/descriptors.go
- registry/client/repository_test.go 2 additions, 2 deletionsregistry/client/repository_test.go
- registry/handlers/api_test.go 4 additions, 4 deletionsregistry/handlers/api_test.go
- registry/handlers/app.go 1 addition, 1 deletionregistry/handlers/app.go
- registry/handlers/app_test.go 2 additions, 2 deletionsregistry/handlers/app_test.go
- registry/handlers/catalog.go 1 addition, 1 deletionregistry/handlers/catalog.go
- registry/handlers/tags.go 1 addition, 1 deletionregistry/handlers/tags.go
This diff is collapsed.
Please register or sign in to comment