New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CORS HTTP patch request is not working on IE10/11 #1684
Comments
I think that diagnoses the cause, but I am wondering why |
This is weird. In IE8 |
The 1.x fiddle (http://jsfiddle.net/tomchentw/hnL7yt7v/) works fine for me on BrowserStack on IE10/11 (see screenshot from IE11 on Windows 8.1): I'm unable to reproduce the reported bug. |
I'm guessing it might be an issue of IE vm. Any native windows user can help test out? |
That'd be @dmethvin. :-) |
I think there shouldn't be a difference between IE on VM and "real" IE, only diff that could be there if versions are different, @tomchentw could you post your IE 10/11 versions? @mzgol could you do that too? |
Couldn't reproduce that too. IE 10 - 10.0.9200.16384, Windows 8 |
Sure, although, AFAIK, IE10 wasn't updated so drastically as IE11 is during its lifetime. It works for me on: On BrowserStack: On local machines: |
@tomchentw that might mean that you have some policy restrictions in your browser |
@mzgol @markelog I clean installed Yosemite so it took me some time to reinstall PD9 + ModernIE. However, if I switch Frameworks & Extensions from |
Ahh... Silly me. This is because of jsfiddle/jsfiddle-issues#555. Basically, Can you recreate your fiddle on http://jsbin.com/? They're much more responsive than jsFiddle maintainers and the |
OK, here it is: http://jsbin.com/qefabu/1/edit. Click on |
Now in IE11 on Windows 8.1, both via BrowserStack and on a local VM I'm getting errors logged: {
"readyState": 0,
"status": 0,
"statusText": "Error: Permission denied"
} In IE10/IE11 on Windows 7 via BrowserStack I see the error: {
"readyState": 0,
"status": 0,
"statusText": "Error: Could not complete the operation due to error 8070000c."
} Sorry for the fuss with versions and wasting everyone's time, I should've remembered about the change, I made it myself after all. EDIT: fixed the responses, I pasted the wrong ones before. |
Thanks for the update, I updated the first post in this thread to point to that JSbin. I got the same result as you did on (IE10/Win7/ModernIE). |
BTW, jsFiddle has just fixed their links & names for edge versions. |
WOW! Great Open Source. |
Could it be that The ActiveX XHR doesn't cooperate with CORS, at least for PATCH requests? Ideally we would do this in jQuery Compat for XHR on IE:
Am I right? Now it'd be nice to be able to do this without UA-sniffing. |
Or we could just always use the native XHR for cross-domain requests; IE<10 don't have CORS anyway. But then some people might rely on cross-domain PATCH requests working via XDomainRequest if I understand it correctly. |
(IE11/Win8.1/ModernIE) shows the same error, too. |
Sorry but this has gone around a bit and I want to be sure I understand where it stands. Are these two comments from mzgol a correct summary? |
@tomchentw can you summarize the current state of this issue and let us know whether it still exists? |
Let us know if this problem still exists and we can reopen. |
@dmethvin I already updated the first post, and I believe it's clear enough? Repost here: Hey guys, not sure if it's proper to submit issue here. This is really an edge case to reproduce. Prerequest
Some setupThanks to http://httpbin.org/, it's relative easy to reproduce on jsfiddle. ReproducePlease visit this jsfiddle with IE10/11: IE10-Win7-JSBinAs you can see, it will error when I tested with virtual box VM from https://www.modern.ie/ (can any one confirm this issue exists in native windows?). But if you open the link with Chrome/Firefox/Safari, it works like a charm. However, same code setup for jQuery 2 works fine across IE10/11/Chrome/Firefox/Safari: Possible causeAs I dug into the code, I found there's some differences in creating Because we're using |
IE throws an error on cross-domain PATCH requests if issued via the ActiveX interface. This commit switches the logic to use the native XHR in all non-local requests. Fixes jquerygh-1684
@tomchentw Could you check if this works for you with https://dl.dropboxusercontent.com/u/10200888/jquery/jquery-cors.js? I submitted a PR with such a patch: #2183. |
IE throws an error on cross-domain PATCH requests if issued via the ActiveX interface. This commit switches the logic to use the native XHR in all non-local requests. Fixes jquerygh-1684
IE throws an error on cross-domain PATCH requests if issued via the ActiveX interface. This commit switches the logic to use the native XHR in all non-local requests. Fixes jquerygh-1684
Currently don't have an IE environment to test with... |
IE throws an error on cross-domain PATCH requests if issued via the ActiveX interface. This commit switches the logic to use the native XHR in all non-local requests. Fixes jquerygh-1684 Closes jquerygh-2183
jsFiddle broke jQuery Edge URLs; apparently jQuery Compat Edge & jQuery Edge are swapped. :/ See jsfiddle/jsfiddle-issues#600 It's better to use jsbin now: http://jsbin.com/lipaxe/2 EDIT: jsFiddle has been fixed. |
IE throws an error on cross-domain PATCH requests if issued via the ActiveX interface. This commit switches the logic to use the native XHR in all non-local requests. Fixes jquerygh-1684 Closes jquerygh-2183
IE throws an error on cross-domain PATCH requests if issued via the ActiveX interface. This commit switches the logic to use the native XHR in all non-local requests. Fixes jquerygh-1684 Closes jquerygh-2183
IE throws an error on cross-domain PATCH requests if issued via the ActiveX interface. This commit switches the logic to use the native XHR in all non-local requests. Fixes jquerygh-1684 Closes jquerygh-2183
IE throws an error on cross-domain PATCH requests if issued via the ActiveX interface. This commit switches the logic to use the native XHR in all non-local requests. Fixes jquerygh-1684 Closes jquerygh-2183
IE throws an error on cross-domain PATCH requests if issued via the ActiveX interface. This commit switches the logic to use the native XHR in all non-local requests. Fixes jquerygh-1684 Closes jquerygh-2183
IE throws an error on cross-domain PATCH requests if issued via the ActiveX interface. This commit switches the logic to use the native XHR in all non-local requests. Fixes jquerygh-1684 Closes jquerygh-2183
IE throws an error on cross-domain PATCH requests if issued via the ActiveX interface. This commit switches the logic to use the native XHR in all non-local requests. Fixes jquerygh-1684 Closes jquerygh-2183
See #1684 (comment) for latest update.
The text was updated successfully, but these errors were encountered: