Re: [yaco-idsubmit-tool] Fwd: RE: [Tools-discuss] Fwd: [vixie@isc.org: googlebot to the rescue]
"Emilio A. Sánchez" <esanchez@yaco.es> Tue, 26 April 2011 13:39 UTC
Return-Path: <esanchez@yaco.es>
X-Original-To: yaco-idsubmit-tool@ietfa.amsl.com
Delivered-To: yaco-idsubmit-tool@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4D6EE07A4 for <yaco-idsubmit-tool@ietfa.amsl.com>; Tue, 26 Apr 2011 06:39:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.816
X-Spam-Level:
X-Spam-Status: No, score=-1.816 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482, MIME_8BIT_HEADER=0.3, NORMAL_HTTP_TO_IP=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hSGlhh5vzUuA for <yaco-idsubmit-tool@ietfa.amsl.com>; Tue, 26 Apr 2011 06:39:36 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by ietfa.amsl.com (Postfix) with ESMTP id 27FCEE06BC for <yaco-idsubmit-tool@ietf.org>; Tue, 26 Apr 2011 06:39:35 -0700 (PDT)
Received: by wyb29 with SMTP id 29so534379wyb.31 for <yaco-idsubmit-tool@ietf.org>; Tue, 26 Apr 2011 06:39:35 -0700 (PDT)
Received: by 10.227.200.138 with SMTP id ew10mr798797wbb.21.1303825175055; Tue, 26 Apr 2011 06:39:35 -0700 (PDT)
Received: from [192.168.0.197] ([77.227.215.107]) by mx.google.com with ESMTPS id z13sm3852481wbd.63.2011.04.26.06.39.33 (version=SSLv3 cipher=OTHER); Tue, 26 Apr 2011 06:39:34 -0700 (PDT)
Message-ID: <4DB6CB18.5080903@yaco.es>
Date: Tue, 26 Apr 2011 15:39:36 +0200
From: "\"Emilio A. Sánchez\"" <esanchez@yaco.es>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.14) Gecko/20110223 Thunderbird/3.1.8
MIME-Version: 1.0
To: yaco-idsubmit-tool@ietf.org
References: <4DB6C23B.2000008@levkowetz.com>
In-Reply-To: <4DB6C23B.2000008@levkowetz.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
Subject: Re: [yaco-idsubmit-tool] Fwd: RE: [Tools-discuss] Fwd: [vixie@isc.org: googlebot to the rescue]
X-BeenThere: yaco-idsubmit-tool@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion of the Yaco / I-D Submission Tool Project <yaco-idsubmit-tool.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yaco-idsubmit-tool>, <mailto:yaco-idsubmit-tool-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/yaco-idsubmit-tool>
List-Post: <mailto:yaco-idsubmit-tool@ietf.org>
List-Help: <mailto:yaco-idsubmit-tool-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yaco-idsubmit-tool>, <mailto:yaco-idsubmit-tool-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Apr 2011 13:39:37 -0000
Hi Henrik, I'm going to check all the views. Some of them (like approve or confirm view) are used as action in POST forms but if the user makes a GET request by hand the view also does the work. By the way, it seems that the original problem was that a webcrawler was launching actions in the old tool, with the new tool it doesn't happen cause the confirmation link is send by mail and contains a confirmation code so no webcrawler will follow it. But I'm going to do the changes so we respect the HTTP standard :) El 26/04/11 15:01, Henrik Levkowetz escribió: > Hi Emilio, > > Please see below. The observation is correct -- a http GET should not > have side effects, so we need to make the confirmation link return a > web page with a confirmation button (which will do the appropriate POST > which should make the actual confirmation happen. > > > Best, > > Henrik > > -------- Original Message -------- > Subject: RE: [Tools-discuss] Fwd: [vixie@isc.org: googlebot to the rescue] > Date: Mon, 25 Apr 2011 21:56:29 -0700 > From: Dan Wing<dwing@cisco.com> > To: 'Henrik Levkowetz'<henrik@levkowetz.com>, 'Mark Nottingham'<mnot@mnot.net> > CC: 'IETF TOOLS discussion'<tools-discuss@ietf.org> > >> -----Original Message----- >> From: tools-discuss-bounces@ietf.org [mailto:tools-discuss- >> bounces@ietf.org] On Behalf Of Henrik Levkowetz >> Sent: Saturday, March 26, 2011 2:24 AM >> To: Mark Nottingham >> Cc: IETF TOOLS discussion >> Subject: Re: [Tools-discuss] Fwd: [vixie@isc.org: googlebot to the >> rescue] >> >> Hi, >> >> The new draft submission tool doesn't have this problem. > > Just now I used the new submission tool for the first time, and it also > seemed to only need a GET to authorize the actual posting of the I-D. > > -d > > >> I'm about to >> start merging that code to the trunk of the datatracker svn repository >> in something like 10 minutes from now, and do the first deployment >> today. >> >> >> Best, >> >> Henrik >> >> >> >> On 2011-03-23 00:25 Mark Nottingham said the following: >>> In case this hasn't been seen -- it needs to be fixed (i.e., a GET >> shouldn't have such side effects). >>> >>> Cheers, >>> >>> >>> Begin forwarded message: >>> >>>> *Resent-From: *ietf-http-wg@w3.org<mailto:ietf-http-wg@w3.org> >>>> *From: *Stephane Bortzmeyer<bortzmeyer@nic.fr >> <mailto:bortzmeyer@nic.fr>> >>>> *Date: *23 March 2011 12:01:23 AM AEDT >>>> *To: *HTTP Working Group<ietf-http-wg@w3.org<mailto:ietf-http- >> wg@w3.org>> >>>> *Subject: **[vixie@isc.org: googlebot to the rescue]* >>>> *organization: *NIC France >>>> *archived-at: *<http://www.w3.org/mid/20110322130123.GB12433@nic.fr> >>>> >>>> The draft management tool apparently can change the state of a draft >>>> in response to a simple GET... >>>> >>>> Nice violation of the HTTP standard :-) >>>> >>>> *From: *Paul Vixie<vixie@isc.org<mailto:vixie@isc.org>> >>>> *Date: *19 March 2011 2:50:30 AM AEDT >>>> *To: *dnsext@ietf.org<mailto:dnsext@ietf.org> >>>> *Subject: **googlebot to the rescue* >>>> >>>> >>>> i think the 0x20 draft was going nowhere in any case so cancelling >> it is fine. >>>> >>>> 148.68.249.66.in-addr.arpa domain name pointer >>>> crawl-66-249-68-148.googlebot.com<http://crawl-66-249-68- >> 148.googlebot.com>. >>>> >>>> crawl-66-249-68-148.googlebot.com<http://crawl-66-249-68- >> 148.googlebot.com> has address 66.249.68.148 >>>> >>>> it's interesting that it can be done by a web crawler, though. >>>> >>>> re: >>>> >>>> >>>> *From: *IETF I-D Submission Tool<idsubmission@ietf.org >> <mailto:idsubmission@ietf.org>> >>>> *Date: *18 March 2011 10:36:25 PM AEDT >>>> *To: *ipr@ietf.org<mailto:ipr@ietf.org>, dagon@cc.gatech.edu >> <mailto:dagon@cc.gatech.edu>, vixie@isc.org<mailto:vixie@isc.org> >>>> *Subject: **Submission of draft-vixie-dnsext-dns0x20-00 has been >> Cancelled * >>>> >>>> >>>> This message is to notify you that submission of an Internet-Draft, >> draft-vixie-dnsext-dns0x20-00, has just been cancelled by a user whose >> computer has an IP address of 66.249.68.148. >>>> >>>> The IETF Secretariat. >>>> >>>> >>>> >>>> _______________________________________________ >>>> dnsext mailing list >>>> dnsext@ietf.org<mailto:dnsext@ietf.org> >>>> https://www.ietf.org/mailman/listinfo/dnsext >>>> >>>> >>> >>> -- >>> Mark Nottingham http://www.mnot.net/ >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Tools-discuss mailing list >>> Tools-discuss@ietf.org >>> https://www.ietf.org/mailman/listinfo/tools-discuss >> _______________________________________________ >> Tools-discuss mailing list >> Tools-discuss@ietf.org >> https://www.ietf.org/mailman/listinfo/tools-discuss > > > _______________________________________________ > yaco-idsubmit-tool mailing list > yaco-idsubmit-tool@ietf.org > https://www.ietf.org/mailman/listinfo/yaco-idsubmit-tool
- [yaco-idsubmit-tool] Fwd: RE: [Tools-discuss] Fwd… Henrik Levkowetz
- Re: [yaco-idsubmit-tool] Fwd: RE: [Tools-discuss]… Emilio A. Sánchez
- Re: [yaco-idsubmit-tool] Fwd: RE: [Tools-discuss]… Emilio A. Sánchez