Project

Profile

Help

Issue #7054

Manifest endpoint renders errors with the wrong renderer

Added by mdellweg 4 days ago. Updated 3 days ago.

Status:
NEW
Priority:
Normal
Assignee:
-
Sprint/Milestone:
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:

Description

What it looks like:

$ http get :24817/v2/foo/bar/manifests/1.0
HTTP/1.1 401 Unauthorized
Allow: GET, PUT, HEAD, OPTIONS
Connection: close
Content-Length: 6
Content-Type: */*; charset=utf-8
Date: Mon, 29 Jun 2020 06:29:04 GMT
Docker-Distribution-API-Version: registry/2.0
Server: gunicorn/20.0.4
WWW-Authenticate: Bearer realm="http://localhost:24816/token",service="localhost:24816",scope="repository:foo/bar:pull"
X-Frame-Options: SAMEORIGIN

detail

What it should look like (Content-Type header is important):

$ http put :24817/v2/              
HTTP/1.1 401 Unauthorized
Allow: GET, HEAD, OPTIONS
Connection: close
Content-Length: 111
Content-Type: application/json
Date: Mon, 29 Jun 2020 06:30:34 GMT
Docker-Distribution-API-Version: registry/2.0
Server: gunicorn/20.0.4
Vary: Accept
WWW-Authenticate: Bearer realm="http://localhost:24816/token",service="localhost:24816"
X-Frame-Options: SAMEORIGIN

{
    "detail": "Access to the requested resource is not authorized. A Bearer token is missing in a request header."
}

History

#1 Updated by ipanova@redhat.com 3 days ago

  • Sprint/Milestone set to 2.0.0
  • Triaged changed from No to Yes

Please register to edit this issue

Also available in: Atom PDF