Unexpected behavior in API call response

https://derpibooru.org/50001.json does not behave like I would expect. It HTTP 302s to the homepage.
 
If the image was deleted I would expect the JSON to just say so, or an HTTP 410.

For that matter, the image page does the same thing.

Yeah, but an HTML page 302’ing to an HTML page isn’t really that unexpected. Getting not-JSON from a JSON API call is annoying.

@Xaekai  
I’ll point out that you need to make your code allow for HTML responses at any time. When the site is put into anti-DDoS protection, you will always get HTML back from API.
 
I’d suggest checking the server’s response headers for the content type and accounting for such issues with a graceful timeout/failure mode.