XMLHttpRequest cannot load http://m.agar.io/?_=1430388662333 . No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin ' http://agar.io' is therefore not allowed access. The response had HTTP status code 520.
Yep, I'm getting that too. I think it got a bit too popular and the servers caught on fire.
Agar.io
61–70 of 238 posts
Re: Agar.io
#62While having a quick look at the sources, I learned about the quadtree: http://de.wikipedia.org/wiki/Quadtree . agar.io is using this implementation: https://github.com/silflow/quadtree-javascript to optimize collision detection performance.
Re: Agar.io
#63Re: Agar.io
#64XMLHttpRequest cannot load http://m.agar.io/?_=1430388662333 . No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin ' http://agar.io' is therefore not allowed access. The response had HTTP status code 520.
I'm getting tons of these: WebSocket connection to 'ws://85.159.215.123:443/' failed: Error during WebSocket handshake: net::ERR_CONNECTION_RESET main_out.js:3 socket error
Re: Agar.io
#65And we wonder why we don't have more women, girls and queer folk in technology. Just plain offensive. - edit To be clear, the ridiculous names people are using are offensive. Game was fun until the children showed up.
Re: Agar.io
#66Re: Agar.io
#67Re: Agar.io
#68Wow, this is really fun. Feature request: * minimap * visible world borders
Re: Agar.io
#69Also like everyone else I get connection errors. It's actually quite interesting. It appears this game is load balanced between three or four servers. The script makes a request to " rel="nofollow">http://m.agar.io/?_= which returns the IP of a server used to initiate a websocket. It changes each time you refresh it.
Re: Agar.io
#70XMLHttpRequest cannot load http://m.agar.io/?_=1430388662333 . No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin ' http://agar.io' is therefore not allowed access. The response had HTTP status code 520.
So if for instance your page makes a CORS request and the MySql server is away. Your app framework catches the error and renders the 500 message, but it doesn't automatically set the CORS.
Now your page receives a response that just gets flat out rejected, you can't even inspect it in the network tab.
The easiest solution is probably to set the CORS headers in NGINX.