-
-
Notifications
You must be signed in to change notification settings - Fork 596
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No 'Access-Control-Allow-Origin' header is present on the requested resource #38
Comments
Same problem. slow queries 9/10 followed by XMLHttpRequest cannot load https://api.parse.com/1/classes/tickets. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://www.mysite.com' is therefore not allowed access. The response had HTTP status code 503. this is also presenting the following error Error: 100 XMLHttpRequest failed: {} |
When does this start happening to you? |
I wasn't in the office, By my colleagues have said around 1 - 2 hours ago. 90% of queries are failing by the look of it. No code on our app has been changed in a good few weeks and it has worked perfectly until today. |
I see, for me even a simple query(not nested or with any "where"s) fails for most of the time. |
I think it must be down too Parse.com's service status as Now even loading data directly through there interface isn't working for me. So I doubt this is a JS SDK error and just there side. |
Yes, their backend is not working for me now either... |
Working. Must have been that service error. |
Thank you for your feedback. We use the issue tracker here to track valid bugs in our SDK. Your question seems to be more about how to use Parse. Could you check out the following resources?
|
I am querying some data using the JS SDK. It has been working for me however today when I run it again I get no data returned but the following in console:
XMLHttpRequest cannot load https://api.parse.com/1/classes/MyClass. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://192.168.0.108:8100' is therefore not allowed access. The response had HTTP status code 502.
But I have changed nothing in my code or on the Parse core...
The text was updated successfully, but these errors were encountered: