W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > May to August 1997


From: Yaron Goland <yarong@microsoft.com>
Date: Fri, 25 Jul 1997 15:19:23 -0700
Message-Id: <11352BDEEB92CF119F3F00805F14F4850332A79B@RED-44-MSG.dns.microsoft.com>
To: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com, "Roy T. Fielding (E-mail)" <fielding@ics.uci.edu>, "Jim Gettys (E-mail)" <jg@w3.org>, "Larry Masinter (E-mail)" <masinter@parc.xerox.com>
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/3928
1) HTTP 1.0 script is written which expect to get GETs.
2) HTTP 1.0 resource is programmed to redirect with a 301/302 to the
HTTP/1.0 script
3) Server is upgraded to HTTP/1.1 but the HTTP 1.0 resource and the HTTP
1.0 script are not upgraded.
4) HTTP/1.1 browser comes along and sends a POST to the HTTP 1.0
resource and receives a 301/302. HTTP/1.1 browser sends a POST to the
HTTP 1.0 script. The HTTP 1.0 script gets completely confused because it
was expecting a GET and the user never sees the proper data.

My suggestion is, as horrible as this is going to sound, that we change
the definition of 301/302 to redirect to GET and make 303/304 be
redirect, permanently or temporarily, with the same method. We can't
force the whole world to rewrite all their scripts and our users aren't
going to accept "Well gee, you know, the script is doing the wrong
thing, it should send a 303 not a 301/302."

Received on Friday, 25 July 1997 15:24:25 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:40:20 UTC