[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: LYNX-DEV Download recovery for lynx?

From: Benjamin C. W. Sittler
Subject: Re: LYNX-DEV Download recovery for lynx?
Date: Sun, 10 Aug 1997 16:15:05 -0600 (MDT)

Resumed transfers are part of the HTTP 1.1 specification; basically, a
client can request any byterange from a URL.

As for ncftp, it seems to REGET just fine.

On Sun, 10 Aug 1997, Wayne Buttles wrote:

> On Sun, 10 Aug 1997, John wrote:
> > Hynek Med wrote:
> > > 
> > > On Sun, 10 Aug 1997, David Woolley wrote:
> > > 
> > > > If the file is available by ftp (and it probably should be, but is
> > > > increasingly less likely to be) and you are using Unix, the de facto
> > > > position (its actually a protocol violation) is that the standard ftp
> > > > client will allow transfers to be restarted.
> HUH?  Until this discussion, I was 99% positive that resuming an ftp
> transfer was just an official extention to FTP.  Now I am having a hard
> time tracking down a document to substantiate my claim. 
> Anyhow, REGET is an extended FTP command (legal or not) that needs to be
> covered by the server and client.  The client sends a reget command with
> the bytecount of where the transmition got stopped and the server resumes
> from there. 
> > > > I've yet to find a Windows
> > > > ftp client that does this, so I think you should also complain as to
> > > > why you can't restart ftps in Windows.
> Well, since they have ncftp for Win32...Win95 and NT can resume an ftp
> transfer.  I am sure many clients support it by now. 
> The original question involved a non-free plug in so (apparently)
> http-resume's are not a standard thing.  When Netscape/IE support it
> internally or it pops up in a http draft then I am sure someone will pop
> it in.  

; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]