# Jsfiddle demonstrating IE11 difference talking to nginx vs google

**URL:** <https://www.ruby-forum.com/t/jsfiddle-demonstrating-ie11-difference-talking-to-nginx-vs-google/241751>\
**Category:** NGINX\
**Created:** [April 28, 2015, 5:13pm UTC](https://www.ruby-forum.com/t/jsfiddle-demonstrating-ie11-difference-talking-to-nginx-vs-google/241751 "2015-04-28T17:13:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![musicdenotation](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/ea666f/32.png) [@musicdenotation](https://www.ruby-forum.com/u/musicdenotation)\
**Post date:** [April 28, 2015, 5:13pm UTC](https://www.ruby-forum.com/t/jsfiddle-demonstrating-ie11-difference-talking-to-nginx-vs-google/241751/1 "2015-04-28T17:13:57Z")

</div>

See, or please try:

> **[FileUploadCtrl - JSFiddle - Code Playground](https://jsfiddle.net/qe44nbwh/)**
>
> Test your JavaScript, CSS, HTML or CoffeeScript online with JSFiddle code editor.

If you see what I see in my IE11, when I press Start Test, and the  
target  
is [nginx.org](http://nginx.org), the duration for each request goes slow/normal/slow/normal

But when I change [nginx.org](http://nginx.org) to [google.com](http://google.com), the timing is  
normal/normal/normal …

This only happens with IE11, other browsers behave normally  
(they all do normal/normal/normal timings)

Why would IE11 be sensitive to an nginx server, and not to google ?  
What is nginx doing that google is not doing…

---

<div class="post-metadata">

**Author:** ![jbjbjb](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/82dd89/32.png) [@jbjbjb](https://www.ruby-forum.com/u/jbjbjb)\
**Post date:** [April 28, 2015, 9:09pm UTC](https://www.ruby-forum.com/t/jsfiddle-demonstrating-ie11-difference-talking-to-nginx-vs-google/241751/2 "2015-04-28T21:09:59Z")

</div>

Hello!

On Wed, Apr 29, 2015 at 01:13:37AM +1000, jb wrote:

> (they all do normal/normal/normal timings)
> 
> Why would IE11 be sensitive to an nginx server, and not to google ?  
> What is nginx doing that google is not doing…

It looks like a combination of the following factors:

- for some reason IE11 closes connections after JS requests to  
[nginx.org](http://nginx.org) in your test;

- when IE11 have to open a connection, it opens 2 of them.

As a result, every second request request uses pre-cached connection  
established previously, and it is fast. Others have to wait while  
a connection is established.

No idea why IE closes connections, but it doesn’t happen on normal  
use. May be some bug, or heuristics, or a security measure (as  
the test triggers CORS errors).

–  
Maxim D.

> **[nginx](http://nginx.org/)**