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
I ran into an issue where a library I was testing would crash when issuing a GET /servers/{id}/devices/{id}/ for a device that doesn't exist. In this case, Zetta returns a 404 with the body "Device does not exist". However, the Content-Type header is still application/vnd.siren+json. The library saw the JSON content type and was automatically parsing the body which is not valid JSON.
This isn't a huge issue, but I thought I'd see what your thoughts on fixing this are.
The text was updated successfully, but these errors were encountered:
I'm up for fixing it not sure the best approach. Should we return a value JSON body with a error message? Should we change the Content-Type to text/plain? @kevinswiber Any thoughts from the Siren expert.
I ran into an issue where a library I was testing would crash when issuing a
GET /servers/{id}/devices/{id}/
for a device that doesn't exist. In this case, Zetta returns a 404 with the body "Device does not exist". However, theContent-Type
header is stillapplication/vnd.siren+json
. The library saw the JSON content type and was automatically parsing the body which is not valid JSON.This isn't a huge issue, but I thought I'd see what your thoughts on fixing this are.
The text was updated successfully, but these errors were encountered: