Quantcast
Channel: The Echo Nest Developer Forum
Viewing all articles
Browse latest Browse all 1582

JSONP with error (non-200) intercepted by browsers

$
0
0

Hey Ned, thanks for chipping in

So when making requests from the client, the only way to handle errors is in a generic 'catch all' way

Just so i can understand...

Why are the CORs headers missing from non 200 responses?

Is it by design or a limitation?

Seems a little incomplete that the response cannot be communicated to the original requester

{"response": {"status": {"version": "4.2", "code": 1, "message": "1|Invalid key: Unknown"}}}

Viewing all articles
Browse latest Browse all 1582

Trending Articles