W3C home > Mailing lists > Public > public-html@w3.org > November 2007

Re: Feedback on the ping="" attribute (ISSUE-1)

From: Julian Reschke <julian.reschke@gmx.de>
Date: Tue, 13 Nov 2007 18:19:29 +0100
Message-ID: <4739DCA1.509@gmx.de>
To: Jon Barnett <jonbarnett@gmail.com>
CC: "public-html@w3.org" <public-html@w3.org>

Jon Barnett wrote:
> On Nov 13, 2007 3:32 AM, Julian Reschke <julian.reschke@gmx.de> wrote:
>> Jon Barnett wrote:
>>
>>> And the only reason for making that point is to show why POST is
>>> appropriate for @ping - it performs an action that shouldn't be
>>> repeated by accident.  In the case of @ping, the user doesn't need to
>>> see a warning because the final destination was a GET request, but the
>>> browser knows not to repeat the POST request without explicit action
>>> >from the user (actually clicking the link that causes the ping).
>> Sorry, no. A refresh of a page doesn't constitute what HTML5 calls
>> "following a hyperlink". That is, refreshing a page (or accessing it
>> again through bookmarks) will never initiate the "ping", so what you say
>> is not relevant for our discussion.
> 
> We're saying the same thing here.  The ping should not be repeated
> just by simply pressing the refresh button.  The ping is a POST
> request, and shouldn't be repeated without the user's explicit action
> (clicking the hyperlink).  This is why POST is appropriate.  Where do
> we disagree here?

If we user clicks the link again, it should be repeated. If the user 
refreshes the page containing the link, nothing should happen. If the 
user refreshes the page being linked to, nothing should happen.

So I'm not sure what we're discussing here. The "ping" should be send 
every time the user follows the link, right? I don't see how this is an 
argument for or against an unsafe method.

BR, Julian
Received on Tuesday, 13 November 2007 17:20:17 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:09 GMT