You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The api call /notifier/api/v1/notification/{id} returns with Content-Type: text/plain where application/json is expected. Even if we specify the application/json in the accept header, we still get a plain text response. Would be great if this could be fixed in the upcoming 4.4 release.
Expected Outcome
Content-Type: application/json
Actual Outcome
Content-Type: text/plain
Environment
N/A
Clair version/image: 4.3.5
Clair client name/version:
Host OS: Docker Container on AWS ECS
The text was updated successfully, but these errors were encountered:
This updates the notification endpoints to be more in-line with the
new all-in-one, interally instrumented handler style. It also includes
a change for making the instrumentation code less verbose.
Closes: quay#1523
Signed-off-by: Hank Donnay <hdonnay@redhat.com>
This updates the notification endpoints to be more in-line with the
new all-in-one, interally instrumented handler style. It also includes
a change for making the instrumentation code less verbose.
Closes: quay#1523
Signed-off-by: Hank Donnay <hdonnay@redhat.com>
Description of Problem / Feature Request
The api call
/notifier/api/v1/notification/{id}
returns with Content-Type: text/plain where application/json is expected. Even if we specify the application/json in the accept header, we still get a plain text response. Would be great if this could be fixed in the upcoming 4.4 release.Expected Outcome
Content-Type: application/json
Actual Outcome
Content-Type: text/plain
Environment
N/A
The text was updated successfully, but these errors were encountered: