27

I am working to dynamically create a UI from XML using jQuery. My jQuery is working in Firefox but in Chrome it's not working. It gives me this console error:

Cross origin requests are only supported for protocol schemes: http, data, chrome, chrome-extension, https, chrome-extension-resource.

The following is my jQuery code which working on Firefox but not working on Google chrome:

$.ajax({
    url: 'file:///home/satendra/dndExamples/avisDnD/file.xml',
    success: function(xml) {
        $(xml).find('Tab').each(function() {
            var id = $(this).attr('URL');
            var tab = $(this).attr('TabName');
            $("ul").append("<li><a href="+ id +">"+ tab +"</li>");
        });
    }
});
Improve this question
2
  • 2
    Why are you using file:/// in the first place!? Set a local server. Commented Jul 13, 2016 at 6:58
  • The url should some thing like http url not file path Commented Jul 13, 2016 at 6:59

1 Answer 1

Reset to default
30

Firefox allows the request because it accepts requests to the local file system (ie. the file:// protocol) if they originate from there too. However Chrome denies all XMLHttpRequests to file:// urls.

Note that you cannot make an AJAX request to the local file system from an external domain in either browser - it would be a massive security flaw if you could.

For this AJAX request to work in Chrome you need to make the request to a webserver. If you're on Windows you can easily install IIS or WAMP on your local machine.

Note that it is possible to enable a setting in Google Chrome which allows requests to the local file system from the browser, but it's really not a good idea to use it. If you decide you want to go ahead and do this anyway, a guide can be found here.

Improve this answer
Sign up to request clarification or add additional context in comments.

16 Comments

it can be done, but will have to change the setting of chrome first, which is definitely not advisable but can be done
@Deep true, but that's not a good idea as it leaves your machine very vulnerable.
totally agree with you on this.
I added a note about it if the OP wants to, but it's entirely caveat emptor
The security setting is update on/in the Chrome browser itself! (Global setting) So doesnt matter if the user is trying to load a local file.. if they go a webstie, that has some js code in it.. it can access files in your local file system.
|

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.