We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When requesting non-streaming response type (application/json), /routing/v1/peers returns HTTP 500 instead of 404.
application/json
This in turn makes our infra swap payload into text/html error response.
text/html
Example:
According to current specs, we should return HTTP 404: Ref. https://specs.ipfs.tech/routing/http-routing-v1/#response-status-codes-0
Assuming a bug?
The text was updated successfully, but these errors were encountered:
This is a bug... in Boxo. I will take care of it.
Sorry, something went wrong.
@lidel ipfs/boxo#601
hacdias
Successfully merging a pull request may close this issue.
Problem
When requesting non-streaming response type (
application/json
),/routing/v1/peers returns HTTP 500 instead of 404.
This in turn makes our infra swap payload into
text/html
error response.Example:
Solution
According to current specs, we should return HTTP 404:
Ref. https://specs.ipfs.tech/routing/http-routing-v1/#response-status-codes-0
Assuming a bug?
The text was updated successfully, but these errors were encountered: