3 ms·
omg I saw this once. The status code was 200 but the HTTP body was literally "403: Forbidden". On an endpoint that was supposed to return XML . I guess they
by fenwick67 9y ago
omg I saw this once.
The status code was 200 but the HTTP body was literally "403: Forbidden". On an endpoint that was supposed to return XML .
I guess they just read the spec and assumed "the API returns a '403: Forbidden' " meant this.
- themoat 9y agoI wish I only saw this once. This is my life. I integrate with 3rd party APIs for a living...what I've learned is that everyone's 'REST' API is terrible in one way or another.
- boubiyeah 9y agoAll my clients do that. They literally think that REST means "JSON over HTTP" and don't bother with anything else :(