HTML response with 502 error from API end-point

[AlexWayfer]

@BarryCarlyon

It’s also worth modifying your code to test the HTTP response code first, before trying to JSON parse.

It’s non-sense. It’s also worth modifying your, Twitch, code to return JSON template (from nginx or something else) instead of HTML. For API end-points. It’s not too hard.

@BarryCarlyon

5xx’s codes normally won’t return as JSON response

Why? Where is this “normal” described? Why HTML responses becomes “normal” for API end-points?

@BarryCarlyon

but a Generic “everything is super broken” HTML message

Why there is an HTML message at API end-point with JSON convention? Documentation says there will be JSON response. Is there any information about exclusive cases with HTML format?

@BarryCarlyon

So just retry the request.

So just change low-level error template from HTML to JSON.

@BarryCarlyon

as while most 4xx responses will return a JSON blob describing the error, they might not always.

Any documentation about these cases?

@BarryCarlyon

Same for 200’s sometimes you’ll get a 200 but something went wrong and you didn’t get JSON back, so you should code to account for the possibility of not getting JSON back.

It’s also non-sense. You’re saying me “just retry a request”. And what next? What if something changed and there will be always “just retries”? These cases, HTML responses, are exception for JSON API, they should not be there in any time. If you could make HTML low-level error — you can make JSON template in the same way. So, please, do it. For API end-points (by domain, servers, anything else, as you want).