Cross-Origin Resource Sharing (CORS) Support
Beth Castillo commented
It looks like this has been requested for a long time now. I've been trying to figure out this error spawned in my codepen.io app and finally figured out it's a cors thing:
"XMLHttpRequest cannot load https://bibles.org/v2/passages.js?q=john+3:1-5&version=eng-KJVA,eng-GNTD. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://s.codepen.io'; is therefore not allowed access. The response had HTTP status code 401."
Ryan Schie commented
This is immensely helpful and completely necessary for any front-end API consumption. I know it would add a world of delight to any developer using the API.
Steven Valladolid commented
This is huge with the rise of decoupling client and server development. Until this is officially supported by the API, development is underway on a Node.js proxy server: https://github.com/mellatone/bible-search-node-proxy
Crafton Williams commented
Definitely agree, this is highly necessary.
Mark Breneman commented
I agree CORS is badly needed. I had a prototype AngularJS project mocked up in 20 mins, then spent the next 3 hours tracking down the access denied errors, to find that it is really a No 'Access-Control-Allow-Origin' header is present on the requested resource. CORS issue. Please don't make me add a Proxy server, just to get CORS support.
Jürgen Roderick Visser commented
We definitely need this for modern browser-based applications. I myself use AngularJS.