Got "Cross-Origin Request Blocked" but works in Chrome
When first access http://s.phono.com/releases/1.1/samples/kitchen-sink/www/index.html, it's OK but when I refresh the page I got the following annoying error in the Web Console:
"Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://pgw-v11f.phono.com:8080/http-bind. This can be fixed by moving the resource to the same domain or enabling CORS."
I've checked the Headers is fine. I'm using Firefox 31.0
But all works in a Chrome 36.0.
Toutes les réponses (12)
Ya change the feature to number 2. network.http.referer.XOriginPolicy or security.fileuri.strict_origin_policy -> false
After I set both, still got the same security error on refresh. You can easily reproduce it.
After I set both, still got the same security error on refresh. You can easily reproduce it.
I see that you are using CORS apihttp://www.bennadel.com/blog/2327-cross-origin-resource-sharing-c...
I tested the site in version 32, beta and it seems to be working ok, can you try beta to make sure it is also working on your end?
I've installed the beta and updated to RC1 later, I still have this issue when I refresh the page.
I went to the link you posted. I reloaded the page several times using F5 and Shift F5. There were no problems.
http://s.phono.com/releases/1.1/samples/kitchen-sink/www/index.html
Thanks for your response. Have you opened the Web Console? There should be one Warning during the reloading of the page.
Does this also happen after the update to version 32?
The error occurs after I hit the back button after testing the chat:
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://pgw-v11f.phono.com:8080/http-bind. This can be fixed by moving the resource to the same domain or enabling CORS.
Not when forward. Did changing the origin feature in about:config show this warning?
>>Does this also happen after the update to version 32? Yes >>Did changing the origin feature in about:config show this warning? Using this "Ya change the feature to number 2. network.http.referer.XOriginPolicy or security.fileuri.strict_origin_policy -> false " did not help.
Are these headers the same?
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:33.0) Gecko/20100101 Firefox/33.0 Referer: http://s.phono.com/releases/1.1/samples/kitchen-sink/www/index.html Pragma: no-cache Origin: http://s.phono.com Host: pgw-v11g.phono.com:8080 Content-Type: text/plain; charset=UTF-8 Content-Length: 496 Connection: keep-alive Cache-Control: no-cache Accept-Language: en-US,en;q=0.5 Accept-Encoding: gzip, deflate Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Modifié le par guigs
Mine: User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:33.0) Gecko/20100101 Firefox/33.0 Referer: http://s.phono.com/releases/1.1/samples/kitchen-sink/www/index.html Pragma: no-cache Origin: http://s.phono.com Host: pgw-v11f.phono.com:8080 Content-Type: text/plain; charset=UTF-8 Content-Length: 110 Connection: keep-alive Cache-Control: no-cache Accept-Language: en-US,en;q=0.5 Accept-Encoding: gzip, deflate Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Please NOTE: I only got this error when refreshing this page.
Is this because of cookies expiring on the same session id?