I am wondering if the response header needed is the one below: Access-Control-Allow-Origin: *
Reviewing the documentation for Access-Control-Allow-Headers, the header responds to a browser’s pre-flight request (which includes a Access-Control-Request-Headers header from the client-side).
My hypothesis is that that may not be directly related to the issue at hand. It seems that addition of the Access-Control-Allow-Origin: * response header would solve the CORS issue as it would allow calls from any origin instead of just http://type.fit.
Sorry for bugging you on this! This is first time I am running into a CORS issue so I have been forced to finally learn it, which is fantastic.
Having the same issue as ab91. I’m also a novice with these things but I thought I’d chime in anyway. I’ll be following along
Question, I’m working with my app on “localhost”, would this cause the issue since perhaps my localhost server isn’t permitted to access the url?
Hi, I was also using this API and it stopped working due to the CORS issue. This is such a cool API, thanks for building it! I hope you can get it up and running again. We appreciate it so much.
That is a killer update! Thanks for your work. I temporarily am using another service for this, but the quotes are not as good. I’ll revert to yours in a bit, I see the more permissive header is in there now.
Hi ,thanks a lot for the API .I wanted to know that can i use it in my production website i have already created a simple website link: https://hasbeenquoted.herokuapp.com/ . Thanks again really appreciate your help.