```json
{
    "title": "Internet Explorer: Plan to completely support RFC 2616 anytime before the next ice age?",
    "url": "https://performancezen.com/2007/03/13/internet-explorer-plan-to-completely-support-rfc-2616-anytime-before-the-next-ice-age/",
    "datePublished": "2007-03-13",
    "dateModified": "2022-05-12",
    "language": "en-US",
    "description": "I am writing up a client presentation for next week, and I just realized just how flawed Internet Explorer is. Microsoft claims that the browser is standards compliant. Yet it…",
    "author": "spierzchala",
    "publisher": "Performance Zen"
}
```

# Internet Explorer: Plan to completely support RFC 2616 anytime before the next ice age?

I am writing up a client presentation for next week, and I just realized just how flawed Internet Explorer is. Microsoft claims that the browser is standards compliant. Yet it **still** doesn't support HTTP pipelining.

And the frustrating part? They won't tell us why. I have my suspicions, which include TCP stack issues and a flawed HTTP handling mechanism that is still based on Windows 95 architecture, but an explanation from Redmond would be nice.

Every (and I mean *every*) other browser can do this.

Microsoft, it's time you detached your Web browser from your OS, like you've forced everyone else to do.