-
Notifications
You must be signed in to change notification settings - Fork 27.5k
IE8 CORS support #934
Comments
http://www.nczonline.net/blog/2010/05/25/cross-domain-ajax-with-cross-origin-resource-sharing/ in IE8 we need to use
|
Thanks - posted as "issue" in case you wanted to make IE8 support transparent in Angular. Not a major for me - so close if you wish. |
it seems that XDomainRequest has some limitations and jquery is hesitant to include it in the core: http://bugs.jquery.com/ticket/8283 |
@IgorMinar do we want to support the Maybe we should then close this issue and make it clear that |
Hi all, Sorry to dredge up an old thread; any further thoughts on this? Most of the group posts and other PRs just lead to dead ends. |
Has anyone ever tried to use flXHR to fix this? Running into the exact same problem 😢 |
On 2012-05-07 @IgorMinar wrote:
Since this comment, someone updated that ticket with:
The XDR transport for jQuery is at: https://github.com/jaubourg/ajaxHooks/blob/master/src/xdr.js Thought I'd post in case it's helpful to anyone watching this. |
pending workaround for angular/angular.js#934
I finally managed to get CORS working in IE8 and while this is definitively not for everyone here is a quick run-down on what I did: In general I used flXHR as a Flash driven XHR drop-in replacement. We decided that it is ok to require Flash for our IE audience. Here are the caveats I experienced during the implementation: Flash does only support POST or GET methodsAs our backend is written in Ruby the solution here was a small rack middleware that takes a Flash does not support empty bodies for POST methodsWe built a small wrapper around flXHR that adds a dummy body whenever it was empty. Flash does not allow you to send
|
Used this snippet, but there's some problem with resolving relative paths, that're not starting with slash, i.e. : 'views/main.template.html' is resolved to '@hostname/views/main.template.html' instead '@hostname/@pathname/views/main.template.html', so in case you're using this, added
at line 60-62 in "send" function. |
If someone was referred here by a search engine: I managed to implement CORS in IE9 and below using https://github.com/jpillora/xdomain, which is a straight-forward implement and it didn't require any modifications to Angular in our project. |
I ended up here, and the solution I eventually used was the jsonp method of $http and using the Yahoo APIs. That got me past CORS issues in IE9 |
+1 on https://github.com/jpillora/xdomain. This really helped in a pinch! |
As per thread: https://groups.google.com/forum/#!searchin/angular/cors/angular/MoQ4pcn08io/eav59m8qzLkJ
The text was updated successfully, but these errors were encountered: