containers list api route response header is text/plain instead of application/json #14647
Labels
In Progress
This issue is actively being worked by the assignee, please do not work on this at this time.
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
/kind bug
Description
Response content-type header is not
application/json
for containers list endpoint, although negotiation requests it.Some client libraries do attempt deserializing automatically to their data structures. Although it can be mitigated as an exception for this route, it should respect the negotiation. (v3 and v4 have the same behavior)
Steps to reproduce the issue:
base url
v3.0.0
-curl -v -X GET --unix-socket "/run/user/1000/podman/podman.sock" "http://d/v3.0.0/libpod/containers/json" -H "Accept: application/json" -H "Content-Type: application/json"
base url
v4.0.0
-curl -v -X GET --unix-socket "/run/user/1000/podman/podman.sock" "http://d/v4.0.0/libpod/containers/json" -H "Accept: application/json" -H "Content-Type: application/json"
Describe the results you received:
Describe the results you expected:
If any use, issued the same for docker api and it does have
application/json
as response content-type headerThe text was updated successfully, but these errors were encountered: