3 ms·
Doing XHR CORS with IE 8 and 9 is infuriating. At first you're tempted to think, ok I can just use XDomainRequest. Well, XDomainRequest is extremely limited. Y
by nodesocket 10y ago
Doing XHR CORS with IE 8 and 9 is infuriating. At first you're tempted to think, ok I can just use XDomainRequest.
Well, XDomainRequest is extremely limited. You can only send text/plain content-types (no JSON). You can't specify custom request headers and the source page and server must be using the same scheme. Basically, XHR CORS on IE 8 and 9 are essentially not possible.
- goatlover 10y agoWhy do you care about supporting IE 8 and 9 at this point? It's almost 2017.
- nodesocket 10y agoWhen your building e-commerce not supporting IE 8 and 9 is lost revenue, potentially a decent chunk.
- jgalt212 10y agoI felt the same way, but recently I went back and checked the logs, and found out that even our most backwards customers who were on IE 8 for the longest time are now on IE 11.
- dcherman 10y agoIt's possible to a degree, but only for pages on the same top level domain, and only if you're willing to relax a bit of security by setting `document.domain`. I wrote an ajaxTransport for jQuery to accomplish this exact thing years ago; I can ask about open sourcing it if there's interest since I doubt it's in use anymore since our browser set is IE10+ at this point.