On Sun, Feb 20, 2000 at 10:08:44AM -0500, John R Levine wrote:
> > You just need to make a form submit button say "Click here to confirm"
> > instead of a link, that's all.
>
> Interesting theory. What about the many millions of users who
> don't use or want HTML mail readers? It's easy enough to pick
> a URL out of a text message and click on it, but you can't do
> that if it's an entire form.
Right... see my response to Tim Pierce (re multipart/alternative)
> But really, this argument is silly. Real web browsers and
> servers treat GETs with arguments the same as POSTs.
No, they treat them quite differently, as they should.
If you try to reload a page that was the result of a POST, the
browser will display a popup saying "Repost form data?" or
somesuch. (At least, all the browsers I've used recently do,
as they're required per the specs.)
And caches treat get and post differently, too.
The relevent specs are (for those interested):
HTTP 1.1 section 9.1: Safe and Idempotent Methods
http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.1
HTML 4.01 section 17.13: Form submission
http://www.w3.org/TR/html4/interact/forms.html#h-17.13
If you know of any browsers that get this wrong, please let me know.
(off the list is fine)
> Whatever theoretical difference may have once existed between
> them stopped mattering about the time that browsers stopped
> implementing PUT.
This is off-topic and not directly relevent, but: which browsers
have stopped implementing PUT? As far as I know it has yet to be
implemented in most browsers; I don't know of any that supported
it in the past and don't today.
(Most publishing at the place I work is done via HTTP PUT, but
they're kind of exceptional.)
--
Gerald Oskoboiny <[EMAIL PROTECTED]>
http://impressive.net/people/gerald/
