jsonp is called instead of json in cross domain requests

[ubershmekel]

This was surprising to me and I'm still not sure how to handle cross-domain jsonp 404 responses.

[JonathanThiyagarajan]

If you are trying to post a data. you could not do it So, You Can use get method in regards with the cross domain, Trying using crossdomain:true, in your ajax call

[ubershmekel]

The jsonp request in question happens on my site for example here http://www.redditp.com/r/qwer/awwasdfasdfasdfa/ note that I do give an error after a timeout though the 404 arrives before the alert pops up. Will crossdomain:true help me catch and handle the 404 event?

[JonathanThiyagarajan]

U can Very handle the 404 Event.

[gnarf]

So long as you are in here, could you separate each of those <li> onto it's own line? It would make this much easier to review. I can tell you from a quick read that you'll want to remove the ...

Also, have you signed the CLA? http://contribute.jquery.org/CLA/

[ubershmekel]

Fixed that and just signed. I'll verify the 404's catchable with crossdomain:true hopefully in ~10 hours.

[kswedberg]

I think this is too vague/incomplete, and I'm not quite sure how to fix it. In which cases does it force a "jsonp request"? Did you verify the catchable 404s? You can make an xhr post or get using CORS and it won't try to use jsonp. You would need to set the xhrFields option:

xhrFields: {
    withCredentials: true
}

[gnarf]

this should be on the previous line.

[gnarf]

@ubershmekel - do you have any updates on this issue specifically for @kswedberg's comment? It seems like one of those awkward edge cases we don't want to document unless we can clearly explain the situation it occurs in.

[arthurvr]

@ubershmekel This PR needs some updates. See comments above. It would be nice if you could do them?

[ubershmekel]

Fixed the complaints and fixed the merge. From my testing crossdomain does not help detect the 404. The 404 being undetectable may be a browser security feature.

[arthurvr]

Thanks @ubershmekel. What do we think @gnarf @kswedberg?

[dmethvin]

I definitely like this formatting better. For this:

Cross-domain requests may invoke "jsonp" unless explicitly "jsonp" is set to false.

I'd change it to something like:

Cross-domain "json" requests are converted to "jsonp" unless the request includes jsonp: false in its request options.

[arthurvr]

ping @ubershmekel

[ubershmekel]

Sorry guys, I was abroad for a few weeks. It's a bit of a pain that every time I come back to this tiny change the pull request has merge conflicts.

I do like the proposed wording. If I fix it per @dmethvin would that be the final iteration?

[arthurvr]

It's a bit of a pain that every time I come back to this tiny change the pull request has merge conflicts.

For now feel free to not care about merge conflicts. I can take care of them while merging.

[ubershmekel]

Rebased with the new wording.

[ubershmekel]

Ping @dmethvin @arthurvr before the next conflict.

[dmethvin]

Whoa, sorry this got buried. LGTM!

[arthurvr]

"xml"

I wonder if these shouldn't be in <code> elements. For the rest this LGTM!

[arthurvr]

I'm going to make that trivial change myself and land this one. Thanks for your hard work, @ubershmekel, and sorry for it taking too long :)