Cross-domain API calls broken?
We’ll take a look, seems like something got missed in the tests.
It’s not just matches.json, other services like map_floor.json and item_details.json are inaccessible as well. I should note that these services are all v1
Yeah, every /v1 API had its CORS headers go missing. They should all be back in place now.
Looks all good to me. Thanks for the quick fix Pat!
Is this still the case for the v2 API?
because i get the following message:
https://api.guildwars2.com/v2/items/12452?lang=en&_=1426522029742. No ‘Access-Control-Allow-Origin’ header is present on the requested resource. Origin ‘http://159.253.7.156’ is therefore not allowed access. The response had HTTP status code 404.
(edited by Eastborn.6089)
Is this still the case for the v2 API?
because i get the following message:
https://api.guildwars2.com/v2/items/12452?lang=en&_=1426522029742. No ‘Access-Control-Allow-Origin’ header is present on the requested resource. Origin ‘http://159.253.7.156’ is therefore not allowed access. The response had HTTP status code 404.
Looks fine to me:
Even our 404 sends a CORS header.