CORS HTTP patch request is not working on IE10/11

[tomchentw]

See #1684 (comment) for latest update.

[dmethvin]

I think that diagnoses the cause, but I am wondering why patch is left out. Is RFC 5789 actually a standard now?

[mgol]

This is weird. In IE8 PATCH is supported only via ActiveX, is it supported in IE10/11 only via native XHR? O_o

[mgol]

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.

[tomchentw]

I'm guessing it might be an issue of IE vm. Any native windows user can help test out?

[mgol]

I'm guessing it might be an issue of IE vm. Any native windows user can
help test out?

That'd be @dmethvin. :-)

[markelog]

IE vm

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?

[markelog]

Couldn't reproduce that too.

IE 10 - 10.0.9200.16384, Windows 8
IE 11 - 11.0.9600.16663, Windows 8.1

[mgol]

@mzgol could you do that too?

Sure, although, AFAIK, IE10 wasn't updated so drastically as IE11 is during its lifetime.

It works for me on:

On BrowserStack:
IE10: 10.0.9200.17028 on Windows 7
IE11: 11.0.9600.17207 on Windows 7, 11.0.9600.16663 on Windows 8.1 (oh, I hoped BrowserStack is updating it more often...)

On local machines:
IE10: 10.0.9200.17116 on Windows 7 (an image from https://modern.ie)
IE11: 11.0.9600.17351 on Windows 8.1 (my private Windows copy installed via BootCamp and run via Parallels)

[markelog]

@tomchentw that might mean that you have some policy restrictions in your browser

[tomchentw]

@mzgol @markelog I clean installed Yosemite so it took me some time to reinstall PD9 + ModernIE.
Yes, I can't reproduce with the fiddle on IE10/win7: http://jsfiddle.net/tomchentw/hnL7yt7v/
It works perfectly.

However, if I switch Frameworks & Extensions from jquery 1.x-master to jquery 1.11.0 and run it again, it is NOT working. Same issue for 1.10.0 and 1.8.3. Any ideas?

[mgol]

However, if I switch Frameworks & Extensions from jquery 1.x-master to jquery 1.11.0 and run it again, it is NOT working. Same issue for 1.10.0 and 1.8.3. Any ideas?

Ahh... Silly me. This is because of jsfiddle/jsfiddle-issues#555. Basically, jquery 1.x-master actually points to the latest commit for the jQuery version that doesn't support IE<9.

Can you recreate your fiddle on http://jsbin.com/? They're much more responsive than jsFiddle maintainers and the jQuery Compat WIP (via git) is what jquery 1.x-master used to be; they've already fixed their links via my PR. Please read http://blog.jquery.com/2014/10/29/jquery-3-0-the-next-generations/ for further context.

[mgol]

OK, here it is: http://jsbin.com/qefabu/1/edit. Click on Run with JS.

[mgol]

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.

[tomchentw]

OK, here it is: http://jsbin.com/qefabu/1/edit. Click on Run with JS.

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).

[mgol]

BTW, jsFiddle has just fixed their links & names for edge versions.

[tomchentw]

WOW! Great Open Source.

[mgol]

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:

1. If request is local, use the ActiveX one.
2. If IE>=9, use native XHR.
3. If IE8 and we're using sth different than get|post|head|put|delete|options, use ActiveX.
4. If IE8 and we're using one of get|post|head|put|delete|options, use the native XHR.

Am I right? Now it'd be nice to be able to do this without UA-sniffing.

[mgol]

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.

[tomchentw]

(IE11/Win8.1/ModernIE) shows the same error, too.

[dmethvin]

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?

[dmethvin]

@tomchentw can you summarize the current state of this issue and let us know whether it still exists?

[dmethvin]

Let us know if this problem still exists and we can reopen.

[tomchentw]

@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

1. Using jQuery 1.x
2. HTTP method is PATCH
3. It's a cross-origin request
4. With browser IE10/11

Some setup

Thanks to http://httpbin.org/, it's relative easy to reproduce on jsfiddle.
However, since we're requiring CORS but this PR (https://github.com/kennethreitz/httpbin/pull/158) is not merged && deployed, I forked and setup server thanks to Heroku: http://http-patch-cors.herokuapp.com/

Reproduce

Please visit this jsfiddle with IE10/11:
http://jsbin.com/qefabu/1/edit

IE10-Win7-JSBin

As 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:
http://jsfiddle.net/tomchentw/meyh6nkw/

Possible cause

As I dug into the code, I found there's some differences in creating xhr object between 1.x and 2.x code:
1.x: http://git.io/h5Fh2A
2.x: http://git.io/6ZpGEA

Because we're using patch method and it's absence in the regex, the statement will use the old window.ActiveXObject( "Microsoft.XMLHTTP" ) and maybe it doesn't support patch method?

[mgol]

@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.

[tomchentw]

Currently don't have an IE environment to test with...

[mgol]

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.

[mgol]

Closed via #2183, laded at 61f812b.