Hmm. Actually looking at the Access-Control-Allow-Origin header of the API I'm using, it appears to be internal. (Oh dear.)
In any case, the bug is still there, and it'd be lovely to get a Access-Control-Allow-Origin header on the normal JSON API, so that it can be used from AJAX calls.
Search found 2 matches
Search found 2 matches • Page 1 of 1
- Wed Feb 24, 2016 11:04 am UTC
- Forum: Site/Forum issues
- Topic: Incorrect encoding on JSONP API
- Replies: 5
- Views: 4034
Today's comic (#1647) has revealed an encoding issue on the alt text of the JSONP-API, which I am using for an info-screen at our office. :) (I cannot use the normal JSON API, since it doesn't set an Access-Control-Allow-Origin-header, and therefore cannot use it for cross-origin requests.) Sadly I ...