Access-Control-Allow-Origin error sending a jQuery

问题:

I read a lot for the \'Access-Control-Allow-Origin\' error, but I don\'t understand what I have to fix :(

I\'m playing with Google Moderator API, but when I try to add new serie I receive:

XMLHttpRequest cannot load 
https://www.googleapis.com/moderator/v1/series?key=[key]
&data%5Bdescription%5D=Share+and+rank+tips+for+eating+healthily+on+the+cheaps!
&data%5Bname%5D=Eating+Healthy+%26+Cheap
&data%5BvideoSubmissionAllowed%5D=false. 
Origin [my_domain] is not allowed by Access-Control-Allow-Origin.

I tried with and without callback parameter, I tried to add \'Access-Control-Allow-Origin *\' to the header. And I don\'t know how to use $.getJSON here, if apply, because I have to add the Authorization header and I don\'t know how to do it without beforeCall from $.ajax :/

Any light for this darkness u.u?

That\'s the code:

<script src=\"http://www.google.com/jsapi\"></script>

<script type=\"text/javascript\">

var scope = \"https://www.googleapis.com/auth/moderator\";
var token = \'\';

function create(){
     if (token == \'\')
      token = doCheck();

     var myData = {
      \"data\": {
        \"description\": \"Share and rank tips for eating healthily on the cheaps!\", 
        \"name\": \"Eating Healthy & Cheap\", 
        \"videoSubmissionAllowed\": false
      }
    };

    $.ajax({

        url: \'https://www.googleapis.com/moderator/v1/series?key=\'+key,
        type: \'POST\',
        callback: \'?\',
        data: myData,
        datatype: \'application/json\',
        success: function() { alert(\"Success\"); },
        error: function() { alert(\'Failed!\'); },
        beforeSend: setHeader

    });
}

function setHeader(xhr) {

  xhr.setRequestHeader(\'Authorization\', token);
}

function doLogin(){ 
    if (token == \'\'){
       token = google.accounts.user.login(scope);
    }else{
       alert(\'already logged\');
    }
}


function doCheck(){             
    token = google.accounts.user.checkLogin(scope);
    return token;
}
</script>
...
...
<div data-role=\"content\">
    <input type=\"button\" value=\"Login\" onclick=\"doLogin();\">
    <input type=\"button\" value=\"Get data\" onclick=\"getModerator();\">
    <input type=\"button\" value=\"Create\" onclick=\"create();\">
</div><!-- /content -->

回答1:

I solved the Access-Control-Allow-Origin error modifying the dataType parameter to dataType:\'jsonp\' and adding a crossDomain:true

$.ajax({

    url: \'https://www.googleapis.com/moderator/v1/series?key=\'+key,
    data: myData,
    type: \'GET\',
    crossDomain: true,
    dataType: \'jsonp\',
    success: function() { alert(\"Success\"); },
    error: function() { alert(\'Failed!\'); },
    beforeSend: setHeader
});

回答2:

I had exactly the same issue and it was not cross domain but the same domain. I just added this line to the php file which was handling the ajax request.

<?php header(\'Access-Control-Allow-Origin: *\'); ?>

It worked like a charm. Thanks to the poster

回答3:

If you have this error trying to consume a service that you can\'t add the header Access-Control-Allow-Origin * in that application, but you can put in front of the server a reverse proxy, the error can avoided with a header rewrite.

Assuming the application is running on the port 8080 (public domain at www.mydomain.com), and you put the reverse proxy in the same host at port 80, this is the configuration for Nginx reverse proxy:

server {
    listen      80;
    server_name www.mydomain.com;
    access_log  /var/log/nginx/www.mydomain.com.access.log;
    error_log   /var/log/nginx/www.mydomain.com.error.log;

    location / {
        proxy_pass   http://127.0.0.1:8080;
        add_header   Access-Control-Allow-Origin *;
    }   
}

回答4:

Yes, the moment jQuery sees the URL belongs to a different domain, it assumes that call as a cross domain call, thus crossdomain:true is not required here.

Also, important to note that you cannot make a synchronous call with $.ajax if your URL belongs to a different domain (cross domain) or you are using JSONP. Only async calls are allowed.

Note: you can call the service synchronously if you specify the async:false with your request.

回答5:

In my case the sub domain name causes the problem. Here are details

I used app_development.something.com, here underscore(_) sub domain is creating CORS error. After changing app_development to app-development it works fine.