(Internet Explorer 9) IE9 returns cached GET response on POST

Reported by:	cyberheroo@arcor.de	Owned by:
Priority:	undecided	Milestone:	1.5
Component:	unfiled	Version:	1.4.3
Keywords:		Cc:
Blocked by:		Blocking:

Description

The latest IE9 Beta returns the response of GET request when you submit a POST to the same URL. Cause of this it is required to allow cache: false also on POST requests I think. (I hope they fix it in the browser but if not you already know it.)

I'm afraid IE9 will be the same desaster as IE6. :/

Attachments (0)

Change History (5)

Changed November 02, 2010 12:30PM UTC by jitter comment:1

Did you consider reporting this bug to Microsoft? https://connect.microsoft.com/IE (check the Getting started section)

Changed November 02, 2010 05:12PM UTC by cyberheroo@arcor.de comment:2

Yeah, but it requires registration and I am not interessted in IE so much. :->

Changed November 03, 2010 01:21AM UTC by snover comment:3

resolution:	→ invalid
status:	new → closed

This is a bug in a beta product. We aren’t going to do anything to work around this issue unless it is present in IE9 final. Please report it upstream.

Changed November 03, 2010 01:57AM UTC by snover comment:4

_comment0:	Since rwaldron asked, specifically this is a violation of RFC 2616 §13.10, which states: \ \ Some HTTP methods MUST cause a cache to invalidate an entity. This is either the entity referred to by the Request-URI, or by the Location or Content-Location headers (if present). These methods are: \ - PUT \ \ - DELETE \ \ - POST → 1288749544501708

Since rwaldron asked, specifically this is a violation of RFC 2616 §13.10, which states:

Some HTTP methods MUST cause a cache to invalidate an entity. This is either the entity referred to by the Request-URI, or by the Location or Content-Location headers (if present). These methods are: PUT DELETE POST

Changed February 04, 2011 06:00PM UTC by EricLaw [MSFT] comment:5

This problem only occurs when there is no data submitted via the POST.

It is not a regression from previous IE versions; the problem manifests more commonly in IE9 because IE9 follows RFC2616 cache heuristic rules. You'll see the same behavior in IE8 if the response to the GET returns an explicit cache lifetime.

Side navigation

#7377 closed enhancement (invalid)