W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > September to December 1996

Re: safe reload POST?

From: Rob Hartill <robh@imdb.com>
Date: Fri, 27 Sep 1996 01:29:26 +0100 (BST)
Message-Id: <199609270029.BAA07060>
To: "Roy T. Fielding" <fielding@liege.ICS.UCI.EDU>
Cc: koen@win.tue.nl, http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/1652
Roy T. Fielding wrote:

>Contrary to unpopular belief, I don't need an IETF-blessed standard
>to tell whether something is broken or not.  Reload is a reLOAD of the
>response, not a REDO of the action that generated that response

So Netscape has a button that does the job of repeating (or REDOing)
a request performed earlier. If they want to label that button "RELOAD"
then that's fine by me and I'll continue to put it to good use to send
more POSTed requests to a server.

If you're saying that the action of (say) Netscape w.r.t to their
reload button is wrong because it doesn't behave exactly as you described
earlier then I think you're wrong... very wrong.

If you want to invent some new browser functionality that does what
you think "reload" means then that's a completely separate issue.
There's no section in any HTTP spec I've seen that describes what browser
buttons should do or be called, though I might have missed it.

Rob Hartill (robh@imdb.com)    
http://www.imdb.com/  ... why wait for a clear night to see the stars?.
Received on Thursday, 26 September 1996 17:38:02 UTC

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