- From: James Graham <jg307@cam.ac.uk>
- Date: Thu, 12 May 2005 23:05:37 +0100
Kornel Lesinski wrote: > On Wed, 11 May 2005 11:28:25 +0100, Mark Wubben <markwubben at gmail.com> > wrote: > >> An example: >> >> <a href="/delete/$id/confirm" action="/delete/$id" >> method="post">delete</a> >> >> What do you think? > > > That it doesn't look like data to send using POST method. > I'm afraid that in most cases it will be used as: > > <a href="#" action="/delete/$id" method="post">delete</a> > > So there must be something that requires authors to use it properly... > Wouldn't it work if a single URL in the the href attribute was used for both request types? i.e. simply <a href="/delete/$id" method="post">delete</a> The serverside application would be expected to deal with GET requests on the URI in a sane way e.g. returning a confirmation page with a POSTable form on it - this would account for legacy clients and allow tools like GWA to work.
Received on Thursday, 12 May 2005 15:05:37 UTC