W3C home > Mailing lists > Public > ietf-discuss@w3.org > November 2001

Re: TFTP URL

From: Mark Baker <distobj@acm.org>
Date: Fri, 30 Nov 2001 01:20:46 -0500 (EST)
Message-Id: <200111300620.BAA03722@markbaker.ca>
To: duerst@w3.org (Martin Duerst)
Cc: discuss@apps.ietf.org
> At 01:26 01/11/25 -0500, Mark Baker wrote:
> > > Think about the "http:".
> >
> >Invokes GET, which is safe.  Yes, an app developer is free to implement
> >unsafe GETs, but any bad stuff that happens is the fault of that
> >developer, not the person doing the GET.
> 
> What about http: in an html form context with method="post" ?

That's the identifier of the resource that does the POST processing.
Invoking GET on that resource is very different than invoking POST ...
just don't tell the browsers, which for some reason assume that if I try
to do a GET on one of those URIs after a POST, that I really meant to
redo the POST.  Sigh.

> What about all other (potential) contexts of URIs?

Not sure what you mean by "contexts".  The "U" stands for "Uniform",
doesn't it? 8-)

I can take this offline if you like.

MB
-- 
Mark Baker, Chief Science Officer, Planetfred, Inc.
Ottawa, Ontario, CANADA.      mbaker@planetfred.com
http://www.markbaker.ca   http://www.planetfred.com
Received on Friday, 30 November 2001 01:22:49 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 23 March 2006 20:11:29 GMT