JSONP Object Error

Question

I am trying to make a cross domain request to send/recieve some data. I can't get past the object error. Before I was getting the No Transport Error but adding Query.support.cors = true; solved this issue.

var url = "http://CROSSDOMAINSERVER:PORT/Service1.svc/GetDataUsingDataContract";
            $.ajax({
                type: 'GET',
                url: url,
                data: 'tool=1&product=Some%20Product&details=9&bogus=should%20not%20pass%20validation', 
                datatype: "jsonp",
                contentType: "application/json",
                success: function (response) {
                    alert(response.data);
                },
                error: function (error) {
                    alert(error.statusText);
                }
            });

If I type the url out in a browser:

 http://CROSSDOMAINSERVER:PORT/Service1.svc/GetDataUsingDataContract?&tool=1&product=Some%20Product&details=9&bogus=should%20not%20pass%20validation

I get the correct response.

{"d":{"__type":"ClientSideData:#ProdResourceToolService","details":"9","product":"Some Product","result":"1","site":"Somewhere, SD","systime":"2\/6\/2013 2:50:20 PM","team":"0000000000","tool":"1","user":"username"}}

When I use ajax it does not submit it to the database or return data, just object error. Does anyone have any suggestions on how to get around this?

I should also specify if I remove http://CROSSDOMAINSERVER:PORT/ from var url when debugging locally I get the correct json response. Why does cross domain not work?

That response is not correct if you really want to do JSONP. The return value from JSONP is supposed to be JavaScript code for a function call, not just plain JSON. — Pointy
– Pointy, Commented Feb 6, 2013 at 21:11
From the last line of the question, it looks like you're running this from the same domain! Are you running this from http://localhost/? — Hari Pachuveetil
– Hari Pachuveetil, Commented Feb 6, 2013 at 21:14
jsonp is the only way to do a cross domain request though right? — atrueresistance
– atrueresistance, Commented Feb 6, 2013 at 21:14
Where did you get the idea of changing $.support.cors to true? If a browser doesn't support cors, making it use cors won't make it any better. — user400654
– user400654, Commented Feb 6, 2013 at 21:20
If you are doing JSONP, you don't need CORS. If you are doing CORS, you don't need JSONP. using them together is just confusing. — user400654
– user400654, Commented Feb 6, 2013 at 21:22

Johan · Accepted Answer · 2013-02-06 21:33:11Z

This is your current response:

{
    "d": {
        "__type": "ClientSideData:#ProdResourceToolService",
        "details": "9",
        "product": "Some Product",
        "result": "1",
        "site": "Somewhere, SD",
        "systime": "2/6/2013 2:50:20 PM",
        "team": "0000000000",
        "tool": "1",
        "user": "username"
    }
}

This is a valid JSON string. However, its not valid JSONP. If possible, make your service wrap the json in a function:

responseFunc({
    "d": {
        "__type": "ClientSideData:#ProdResourceToolService",
        "details": "9",
        "product": "Some Product",
        "result": "1",
        "site": "Somewhere, SD",
        "systime": "2/6/2013 2:50:20 PM",
        "team": "0000000000",
        "tool": "1",
        "user": "username"
    }
});

And in your $.ajax() call, add a property: jsonpCallback: 'responseFunc'.

Also, I would suggest passing the data as an object:

data: { tool: 1, product: 'Some Product' } //etc...

If you can access the service from the serverside without any issues you could create a httphandler (.ashx for example) and let it generate the JSON for you. Then you wouldn't have to deal with the cross domain issues on the client side.

Collectives™ on Stack Overflow

JSONP Object Error

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related