W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > January to April 1995

Re: How are/should redirects of POSTS be handled

From: Jim Seidman <jim@spyglass.com>
Date: Thu, 23 Mar 95 17:47:59 -0600
Message-Id: <9503232347.AA11634@hook.spyglass.com>
To: Jeffrey Perry <perry@openmarket.com>
Cc: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
Jeffrey Perry writes:
>What appears to happen when a POST is redirected is the client attempts a
>GET at the new URL so that the user can fill-in the form again (it may have
>changed when it moved)

There are several pages on the Web ("The Revolving Door" comes to mind)
which, on the basis of form input, redirect you to one of a number of
different pages.  These pages then need to be retrieved using GET.  This
usage appears to be much more common than a redirect where the client is
supposed to POST again on the target system.

At a very early stage of development, Enhanced Mosaic would actually do
another POST after a redirect.  In every case that this happened, it
generated incorrect results (like an "Action not allowed" response).  I
think that switching to GET after a redirect is current practice for most

Jim Seidman, Senior Software Engineer, Spyglass Inc.
Received on Thursday, 23 March 1995 15:52:49 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:16:10 UTC