HTML response with 502 error from API end-point

[AlexWayfer]

@Dist

No, and as there’s no explicit guarantees on the type of response for errors you shouldn’t just assume everything should be JSON.

It’s better to mention this in the documentation. But this subject still not about guarantees, but about specific error.

@Dist

Looks to me from the data you posted originally that the response declared that it wasn’t JSON, the response to your request specifically said it was text/html so if your app just assumes its JSON and errors when it isn’t, that’s on you.

This is correct point, thank you. We can forget about JSON parsing error, it’s actually on me, but the problem still in HTML response. There should not be HTML response. Yes, it’s the server error, but it can be changed, as I wrote.

@Dist

If you believe the service that is returning that reaponse is in error, then you should submit an issue on the twitchdev github so it can be tracked.

OK, I’ll try to post this issue and on User Voice, and on GitHub project, but funny there are no links to them in the “Getting help” section of docs:

@Dist

If on the other hand the service is doing what its designed to do

API service designed to send HTML errors? Seriously, this is intentional behavior? I don’t think so. I think Twitch developers just left default and forget about this, because these are (I hope) rare cases.

@Dist

The intended responses will be JSON, as documented, but unexpected errors haven’t been explicitly guaranteed to be any specific format for all cases.

I know. And this is unexpected error, yes. But… we can just change it, so let’s do it. And then resolve other specific, not unknown theoretic, errors properly. Maybe another change on the server side, maybe some catches at a client side.

@Dist

as well as how you could handle such issues on your end

I didn’t asked “how can I handle such errors?”. I know how to handle, I know that I can handle, I know that this is a good practice generally. But I have specific error and I’m sure that it’s better to resolve it on the server side.