cross-domain .load()
So there are obvious reasons why a cross-domain load() is problematic.
However, trying it out.... $(".something").load("http://crossdomain.com/something");
..jQuery DOES end up requesting the cross-domain url. My server logs on the server-side show it's being requested. There is no error from the browser.
But the content doesn't actually make it into the page. Presumably jQuery ends up doing some kind of jsonp technique... but it doesn't seem to actually be sending a ?jsonp=something parameter.
Anyone know what it's doing exactly? Perhaps I need to resort to .ajax instead of the .load shortcut, so I can specify my own "jsonp" and such?
Update with more weird info: Cross-domain .load() DOES "Just Work" from IE. But not FF. WEIRD.
However, trying it out.... $(".something").load("http://crossdomain.com/something");
..jQuery DOES end up requesting the cross-domain url. My server logs on the server-side show it's being requested. There is no error from the browser.
But the content doesn't actually make it into the page. Presumably jQuery ends up doing some kind of jsonp technique... but it doesn't seem to actually be sending a ?jsonp=something parameter.
Anyone know what it's doing exactly? Perhaps I need to resort to .ajax instead of the .load shortcut, so I can specify my own "jsonp" and such?
Update with more weird info: Cross-domain .load() DOES "Just Work" from IE. But not FF. WEIRD.
Topic Participants
jonathan
Kevin Boudloche