Re: [ftpext] End byte of transfer in FTP

Anthony Bryan <anthonybryan@gmail.com> Sat, 04 December 2010 22:14 UTC

Return-Path: <anthonybryan@gmail.com>
X-Original-To: ftpext@core3.amsl.com
Delivered-To: ftpext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8768128C0E7 for <ftpext@core3.amsl.com>; Sat, 4 Dec 2010 14:14:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.911
X-Spam-Level:
X-Spam-Status: No, score=-2.911 tagged_above=-999 required=5 tests=[AWL=0.088, BAYES_00=-2.599, J_CHICKENPOX_101=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XIx1B3mr7YSm for <ftpext@core3.amsl.com>; Sat, 4 Dec 2010 14:14:22 -0800 (PST)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by core3.amsl.com (Postfix) with ESMTP id 5433828C0E3 for <ftpext@ietf.org>; Sat, 4 Dec 2010 14:14:22 -0800 (PST)
Received: by eyd10 with SMTP id 10so5914375eyd.31 for <ftpext@ietf.org>; Sat, 04 Dec 2010 14:15:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=sMT/5EpNgLeiPud69AKJLfMsB5qlCtIKN3q7134wKMM=; b=Pi/S4/W81Fe0okZtz7pxRfkWfYFTsoEsElxNLmEUCA5Se9BxEMsYlIuJZ9B9UH8tRh oUsTodjAU8L+QlKh1aFDf9tGeBtnwIwR6/GI5q9WGfRelS4rI2560o8vFyOgdwO+ztVd yO2ct2UdwdNIwSD1V6CZ423EsoqcfudZ8ljOA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=MpmtryOtfnK5ulrTsfSpq2KvlQeZ1dVz4M8IRzRtgJDpnvb0JwCeNA+Y03zPxBL8Jr kkkSgBJ5Ccrw96TXwxQRVi/mE5cW3eYi3gD1UWmxeSCmrnNhMWIfevILZKSLmV48Fw7e QMVcmFeoN3BLHBRclEHuACkgqEJk4ZQ/Wkphc=
MIME-Version: 1.0
Received: by 10.213.15.135 with SMTP id k7mr4075686eba.76.1291500941747; Sat, 04 Dec 2010 14:15:41 -0800 (PST)
Received: by 10.213.28.2 with HTTP; Sat, 4 Dec 2010 14:15:41 -0800 (PST)
In-Reply-To: <alpine.DEB.2.00.1012011959520.21860@tvnag.unkk.fr>
References: <AANLkTi=_OsGPMsC=BHtOyHzTTM5vJ1=yW9fYk_Tp1xm7@mail.gmail.com> <alpine.DEB.2.00.1012011959520.21860@tvnag.unkk.fr>
Date: Sat, 04 Dec 2010 17:15:41 -0500
Message-ID: <AANLkTikGmtyrcpbEabBXZAo3ai=z8082RBSrvKSQrzq6@mail.gmail.com>
From: Anthony Bryan <anthonybryan@gmail.com>
To: Daniel Stenberg <daniel@haxx.se>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: ftpext@ietf.org
Subject: Re: [ftpext] End byte of transfer in FTP
X-BeenThere: ftpext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <ftpext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ftpext>, <mailto:ftpext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ftpext>
List-Post: <mailto:ftpext@ietf.org>
List-Help: <mailto:ftpext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ftpext>, <mailto:ftpext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Dec 2010 22:14:23 -0000

On Wed, Dec 1, 2010 at 2:02 PM, Daniel Stenberg <daniel@haxx.se> wrote:
> On Mon, 29 Nov 2010, Tatsuhiro Tsujikawa wrote:
>
>> Issuing ABOR command is workaround but sometimes it does not stop
>> immediately and unused bytes are transfered. Another possible workaround is
>> that just closing data connection and wait for reply from control
>> connection(I've not tested this yet).
>
> curl does FTP range requests that way. It used to just close the transfer at
> the desired end point, and it even works fine with "most" servers while the
> remaining servers we've found requires an ABOR for the server to notice that
> the transfer was indeed closed. And after an ABOR like that, it really is
> hard to re-use the control connection safely, so this kind of "range"
> request certainly has its limitations.

would it be possible to modify REST so that if the FEAT reply included RANGE:

      C> feat
      S> 211- <any descriptive text>
      S>  ...
      S>  REST STREAM RANGE
      S>  ...
      S> 211 end

REST could take a starting point and ending point?

if so, I wonder if servers & clients would want to implement that or
if it's too late in the game.

-- 
(( Anthony Bryan ... Metalink [ http://www.metalinker.org ]
  )) Easier, More Reliable, Self Healing Downloads