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
{{ message }}
This repository was archived by the owner on Sep 20, 2021. It is now read-only.
So status only exists in one case, and it is hard to detect the problem (temporary vs permanent, user error (wrong url) vs resource not found) from the message. IMO it should be present in all cases. Further, I think it is bad to send the full error message to the client, exposing internals.
The text was updated successfully, but these errors were encountered:
For a successful request (https://cp-aec-stg.cert.at/api/1.0/ripe/contact?cidr=83.136.39.0/24), this is the response:
Errors (https://cp-aec-stg.cert.at/api/1.0/ripe/contact?cidr=127.0.0.0/8):
https://cp-aec-stg.cert.at/api/1.0/ripe/contact?cidr=127.0.0.asd23/8
And failed authentication:
So status only exists in one case, and it is hard to detect the problem (temporary vs permanent, user error (wrong url) vs resource not found) from the message. IMO it should be present in all cases. Further, I think it is bad to send the full error message to the client, exposing internals.
The text was updated successfully, but these errors were encountered: