diff options
Diffstat (limited to 'usr.bin/fetch/fetch.1')
-rw-r--r-- | usr.bin/fetch/fetch.1 | 52 |
1 files changed, 10 insertions, 42 deletions
diff --git a/usr.bin/fetch/fetch.1 b/usr.bin/fetch/fetch.1 index f3be659841fa9..20be53dd2f696 100644 --- a/usr.bin/fetch/fetch.1 +++ b/usr.bin/fetch/fetch.1 @@ -1,20 +1,19 @@ -.\" $Id: fetch.1,v 1.26 1998/12/08 13:00:48 cracauer Exp $ -.Dd January 15, 1999 +.\" $Id: fetch.1,v 1.23 1998/05/09 21:39:49 wollman Exp $ +.Dd July 2, 1996 .Dt FETCH 1 -.Os FreeBSD 3.1 +.Os FreeBSD 2.2 .Sh NAME .Nm fetch .Nd retrieve a file by Uniform Resource Locator .Sh SYNOPSIS .Nm fetch -.Op Fl MPablmnpqrtv +.Op Fl MPabmnpqr .Op Fl S Ar size -.Op Fl T Ar timeout .Op Fl o Ar file .Ar URL .Op Ar ... .Nm fetch -.Op Fl MPRlmnpqrv +.Op Fl MPRmnpqr .Op Fl S Ar size .Op Fl o Ar file .Op Fl c Ar dir @@ -103,7 +102,7 @@ under any circumstances, even if the transfer failed or was incomplete. .It Fl r Restart a previously interrupted transfer. .It Fl S Ar bytes -Require the file size reported by +Require file size reported by .Tn FTP or .Tn HTTP @@ -115,9 +114,10 @@ This option is useful to prevent .Nm fetch from downloading a file that is either incomplete or the wrong version, given the correct size of the file in advance. -.It Fl s -Ask server for size of file in bytes and print it to stdout. Do not -actually fetch the file. +.It Fl t +Work around a different set of buggy +.Tn TCP +implementations. .It Fl T Ar seconds Set timeout value to .Ar seconds. @@ -126,10 +126,6 @@ Overrides the environment variables for ftp transfers or .Ev HTTP_TIMEOUT for http transfers if set. -.It Fl t -Work around a different set of buggy -.Tn TCP -implementations. .It Fl v Increase verbosity. More .Fl v Ns \&'s @@ -316,16 +312,6 @@ connection. .Sh SEE ALSO .Xr ftp 1 , .Xr tftp 1 -.Rs -.%A R. Fielding -.%A J. Gettys -.%A J. Mogul -.%A H. Frystyk -.%A T. Berners-Lee -.%T "Hypertext Transfer Protocol \-\- HTTP/1.1" -.%O RFC 2068 -.%D January 1997 -.Re .Sh HISTORY The .Nm fetch @@ -381,21 +367,3 @@ and .Fl b involves a minimum of two round trips (for small replies), one less than other implementations. -.Pp -The -.Tn HTTP -standard requires interpretation of the -.Tn RFC 850 -date format, which does not provide a century indication. Versions of -.Nm fetch -prior to -.Fx 3.1 -would interpret all such dates as being in the 1900s. This version of -.Nm fetch -interprets such dates according to the rule given in -.Tn RFC 2068 : -.Bd -literal -offset indent - o HTTP/1.1 clients and caches should assume that an RFC-850 date - which appears to be more than 50 years in the future is in fact - in the past (this helps solve the "year 2000" problem). -.Ed |