You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 12, 2024. It is now read-only.
This issue is occurring for Angular 1.2.10 and seems to still exist in Git. It is related to #4738 and #4464. Supposedly the above defects were fixed with commit 509ec74 but the fix isn't working as expected in IE9.
The IE debugger shows that the XHR object defines a response attribute but it is null. The response body is contained within a responseText attribute.
So perhaps a better fix for this would be to change httpBackend line 94 from this:
@davidjnelson After digging in further I've discovered that this problem is actually being caused by a non-standard response coming back from our service endpoint. My apologies! Going to close this as invalid.
For information's sake, it looks like the cause of this issue is our use of the xdomain lib and a proxy.html on our service endpoint that initializes both response and responseText.
@davidjnelson I am actually a little curious why the httpBackend implementation was changed from version 1.2.3. That version did what I wish the newer version does. :)
This issue is occurring for Angular 1.2.10 and seems to still exist in Git. It is related to #4738 and #4464. Supposedly the above defects were fixed with commit 509ec74 but the fix isn't working as expected in IE9.
The IE debugger shows that the XHR object defines a
response
attribute but it is null. The response body is contained within aresponseText
attribute.So perhaps a better fix for this would be to change httpBackend line 94 from this:
To something more like this:
The text was updated successfully, but these errors were encountered: