I was able to make cross domain requests with this script using both GET and POST, but in both methods that data I passed in by doing data: 'some=json&c=somedata&callback=somecallback' where not getting through to request object on server side.

This is my call;

var jquery_path = "http://ajax.googleapis.com/ajax/libs/jquery/1.5.1/jquery.min.js";

uri = readabilityServiceURI;

  // loading jQuery asynchronously
  crossdomain.async_load_javascript(jquery_path, function () {
    $(function () {
      // doing get request
      crossdomain.ajax({
        type: "POST",
        url: uri,
        data: 'some=json&c=somedata&callback=somecallback',
        success: function (data) {
            renderingFunction(data);
        },
        error : function(jqXHR, textStatus, errorThrown) {
            renderingFunction(errorData);
        }
      });
    });
  });

Not all servers want to allow passing credentials, maybe this can be configured and not hard coded?

        try {
            xhr.withCredentials = true;
        } catch (e) {}; 

Not sure what's the deal, but as title suggests, POST request does not work in Google Chrome. Running exactly the same code in FireFox works fine.

Network tab of the Chrome Dev Tools shows OPTIONS call with status Failed.
Console shows errors:

• OPTIONS http://crossdomainserver.com/ Origin http://crossdomainclienta.com is not allowed by Access-Control-Allow-Origin.
• XMLHttpRequest cannot load http://crossdomainserver.com/. Origin http://crossdomainclienta.com is not allowed by Access-Control-Allow-Origin.

On the server app I have a break point on Application_BeginRequest. On the Get method it gets hit every time. However, on the POST it never gets hit. I have an impression that Chrome "kills" request and it never reaches server app.

Just to make sure the headers are not the issue, all the following headers a slapped on any response from the server:

Response.AddHeader("Access-Control-Allow-Origin", "*");
Response.AddHeader("Access-Control-Allow-Methods", "GET, POST, OPTIONS");
Response.AddHeader("Access-Control-Allow-Credentials", "true");
Response.AddHeader("Access-Control-Allow-Headers", "Content-Type, Depth, User-Agent, X-File-Size, X-Requested-With, If-Modified-Since, X-File-Name, Cache-Control");
Response.AddHeader("Access-Control-Request-Method", "*");
Response.AddHeader("Access-Control-Request-Headers", "*");

Chrome Version 28.0.1500.71 m

Could you please confirm that it indeed behaves this way on Chrome?

Hi,

I've got 2 reports saying that this doesn't work in IExplorer 8 / IExplorer 9.
I did test it on both when I developed this, but I want to make sure that it does work.

Please help me out and test in any browser, especially in IExplorer (since right now I don't have access to one).

Thanks,