Friday, June 1, 2012

XmlHttpRequest error: Origin null is not allowed by Access-Control-Allow-Origin

I'm developing a page that pulls images from Flickr and Panoramio via jQuery's AJAX support.

The Flickr side is working fine, but when I try to $.get(url, callback) from Panoramio, I see an error in Chrome's console:

XMLHttpRequest cannot load . Origin null is not allowed by Access-Control-Allow-Origin.

If I query that URL from a browser directly it works fine. What is going on, and can I get around this? Am I composing my query incorrectly, or is this something that Panoramio does to hinder what I'm trying to do?

Google didn't turn up any useful matches on the error message .


Here's some sample code that shows the problem:

var url = '';
$.get(url, function(jsonp) {
var processImages = function(data) {

You can run the example online .


Thanks to Darin for his help with this. THE ABOVE CODE IS WRONG. Use this instead:

var url = '';
$.get(url, function(data) {
// can use 'data' in here...

Source: Tips4all


  1. For the record, as far as I can tell, you had two problems:

    You weren't passing a "jsonp" type specifier to your $.get, so it was using an ordinary XMLHttpRequest. However, your browser supported CORS (Cross-Origin Resource Sharing) to allow cross-domain XMLHttpRequest if the server OKed it. That's where the Access-Control-Allow-Origin header came in.
    I believe you mentioned you were running it from a file:// URL. There are two ways for CORS headers to signal that a cross-domain XHR is OK. One is to send Access-Control-Allow-Origin: * (which, if you were reaching Flickr via $.get, they must have been doing) while the other was to echo back the contents of the Origin header. However, file:// URLs produce a null Origin which can't be authorized via echo-back.

    The first was solved in a roundabout way by Darin's suggestion to use $.getJSON. It does a little magic to change the request type from its default of "json" to "jsonp" if it sees the substring callback=? in the URL.

    That solved the second by no longer trying to perform a CORS request from a file:// URL.

    To clarify for other people, here are the simple troubleshooting instructions:

    If you're trying to use JSONP, make sure one of the following is the case:

    You're using $.get and set dataType to jsonp.
    You're using $.getJSON and included callback=? in the URL.

    If you're trying to do a cross-domain XMLHttpRequest via CORS...

    Make sure you're testing via http://. Scripts running via file:// have limited support for CORS.
    Make sure the browser actually supports CORS. (Opera and Internet Explorer are late to the party)

  2. You need to maybe add a HEADER in your called script, here is what I had to do in PHP:

    header('Access-Control-Allow-Origin: *');

    More details in Cross domain AJAX ou services WEB (in French).

  3. Works for me on Google Chrome v5.0.375.127 (I get the alert):

    function(json) {

    Also I would recommend you using the $.getJSON() method instead as the previous doesn't work on IE8 (at least on my machine):

    function(json) {

    You may try it online from here.


    Now that you have shown your code I can see the problem with it. You are having both an anonymous function and inline function but both will be called processImages. That's how jQuery's JSONP support works. Notice how I am defining the callback=? so that you can use an anonymous function. You may read more about it in the documentation.

    Another remark is that you shouldn't call eval. The parameter passed to your anonymous function will already be parsed into JSON by jQuery.

  4. As long as the requested server supports the JSON data format, use the JSONP (JSON Padding) interface. It allows you to make external domain requests without proxy servers or fancy header stuff.

    You can read more in The jQuery Cross-Domain Ajax Guide.

    I've been getting the same error!

  5. It's the same origin policy, you have to use a JSON-P interface or a proxy running on the same host.

  6. we managed it via http.conf file (edited then restqrd http service )

    <Directory "/home/the directory_where_your_serverside_pages_is">

    Header set Access-Control-Allow-Origin "*"

    AllowOverride all

    Order allow,deny

    Allow from all


    in the Header set Access-Control-Allow-Origin "*" , u can put a precise url

  7. For simple html project:

    cd project
    python -m SimpleHTTPServer 8000

    Then browser you file.

  8. In my case, same code worked fine on Firefox, but not on Google chrome.
    Google chrome's Javascript console said:

    XMLHttpRequest cannot load
    Origin is not allowed by Access-Control-Allow-Origin.
    Refused to get unsafe header "X-JSON"

    I had to drop the www part of the ajax url for it to match correctly with the origin url and it worked fine then.

  9. I use Apache server, so I've used mod_proxy module. Enable modules:

    LoadModule proxy_module modules/
    LoadModule proxy_http_module modules/

    Then add:

    ProxyPass /your-proxy-url/ http://service-url:serviceport/

    Finally, pass proxy-url to your script.