I've read the other same origin policy topics here on SO, but I haven't seen any solutions related to the local file system.
I have a web app (In a loose sense of the word) that must be local served. I am trying to load a large amount of data in after the user has loaded the page, depending on what they are doing on the webpage. In Firefox 3.5 and IE8 I am able to use jQuery's AJAX() and GetScript() methods to do this, but in Chrome this fails due to the Same Origin Policy.
nullis not allowed
This happens when I do something simple like
This functions perfectly well in IE & Firefox.
After reading a bunch about this, I decided to try writing directly into the head of the document. In the console in Chrome I typed the following:
This works fine when pasted in the console- the
<script...test.js</script> element is added to the head, evaluated, and content loaded into the DOM.
I've read up on the following SO posts, but they are not describing the problem that I have:
Ways to circumvent the same-origin policy
XMLHttpRequest Origin null is not allowed Access-Control-Access-Allow for file:/// to file:/// (Serverless)
Again, my last resort is to load all the data at the webpage's load- This can cause up to a 10 second delay in loading the webpage that is unnecessary for 90% of the app's users.
Thanks for any suggestions/alternatives!!!