| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
incorrectly stated that they were not implemented.
Document the -d option.
|
| |
|
|
|
|
| |
Don't delete the output file if -r was specified.
|
| |
|
|
|
|
|
|
| |
It was not discussed and should probably not happen.
Requested by: msmith and others
|
|
|
|
|
|
|
|
| |
the type argument to *_HEAD and *_ENTRY is a struct.
Suggested by: phk
Reviewed by: phk
Approved by: mdodd
|
|
|
|
|
|
|
|
| |
is shorter than previously announced by the server.
Tested by asami.
Approved by: jkh
|
|
|
|
|
| |
of the typeset output, tend to make diffs harder to read and provide
bad examples for new-comers to mdoc.
|
|
|
|
| |
transmission of the If-Range HTTP header field.
|
| |
|
|
|
|
| |
Reviewed by: dict(1)
|
|
|
|
|
| |
a bogus error ("parsing URI".) I also fixed an inconsistency in
another fs_status.
|
|
|
|
|
|
|
|
|
| |
of an empty buffer... the output file wasn't readable... also warn that
we can't checksum on stdout and print out the base64 encoded version of the
md5 checksum...
Site to actually return md5 digest: web.golux.com
Verified that fetch was broken: Ken Coar <Ken.Coar@Golux.Com>
|
|
|
|
| |
Complained-about-by: charnier
|
|
|
|
|
|
|
| |
file on the local host.
PR: 10042
Submitted by: Chris Costello <phoenix@calldei.com>
|
|
|
|
|
|
| |
and an error document when the requested resource does not exist. Grrr.
Requested by: asami
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Look at the FTP_PASSIVE_MODE environment variable like the man page says.
PR: bin/9464
Submitted by: John A. Shue <John.Shue@symmetron.com>
Add references to RFC's 1790, 959, 850.
PR: doc/6564
|
|
|
|
|
|
|
| |
(e.g. http://www.host.name/foo:bar)
PR: bin/5072
Submitted by: Takeshi WATANABE <watanabe@komadori.planet.kobe-u.ac.jp>
|
| |
|
|
|
|
| |
described in RFC 2068. Include a reference to same in the manual page.
|
|
|
|
| |
Reviewed by: -current list
|
|
|
|
|
|
| |
Fix usage string. Fix getopt() string. Fix ordering of compatibility options.
fetch.1:
Fix synopsis. Fix ordering of T and t options. Fix minor grammar nit.
|
|
|
|
|
| |
the server. There exists a broken server which sends a few extra
garbage bytes in response to HTTP/1.1 requests.
|
|
|
|
|
| |
don't use it. That's why I'm bringing it in during our "code slush"
Submitted by: Stefan Esser <se@mi.uni-koeln.de>
|
|
|
|
| |
PR: bin/7203
|
|
|
|
|
|
| |
- failed to use authorization parameters passed in the environment, if
/dev/tty could not be opened (i.e. if running from cron)
- mixed use of /dev/tty and stdin for prompt and reading of the result
|
|
|
|
| |
argument, so use `.Tn FreeBSD' instead.
|
|
|
|
|
| |
to the case in question. (Said case being quite clearly defined by
the basic TCP specification, RFC 792.)
|
| |
|
|
|
|
| |
PR: bin/6558
|
|
|
|
| |
around uncommitted for 2 months =(
|
| |
|
|
|
|
| |
cast to that instead of quad_t.
|
|
|
|
|
| |
long (yuk). So give time() what it wants and let the compiler
promote the variable when it is assigned to tv_sec.
|
|
|
|
| |
of broken TCP stack).
|
| |
|
|
|
|
|
|
| |
Also fixed some "didn't make the most sense" problems.
Submitted by: bde
|
| |
|
|
|
|
| |
previous change about #? parms
|
|
|
|
| |
Require to correctly parse http://...cgi?http://...
|
|
|
|
|
|
|
| |
is contrary to RFC1738, which specifies that empty elements between
slashes really mean to send a CWD command with an empty argument.
Most FTP servers consider this an error, so strict RFC compliance
is advisable in this case.
|
|
|
|
|
|
|
| |
slash-seperated element of the URL and then RETR the last element.
PR: bin/4670
Reviewed by: wollman
|
|
|
|
|
|
| |
PR: bin/4625
Submitted by: "Timo J. Rinne" <tri@pooh.tky.hut.fi>
Obtained from:bin/4625
|
|
|
|
|
|
| |
there even was one of them about ten lines above in the same file.)
Reminded by: joerg's commit to usr.bin/ftp/ftp.c rev 1.9
|
|
|
|
| |
Submitted by: Marc Slemko <marcs@znep.com>
|
|
|
|
|
|
|
|
| |
for ftp: URLs as well. This can't possibly be done in the general case,
but since we only claim to support http and ftp, we'll adhere to the
bogus requirement (RFC 2068, s. 14.25) anyway... >sigh<
Submitted by: =?iso-8859-1?Q?=C5ge_R=F8bekk?= <aagero@aage.priv.no>
|
|
|
|
|
|
| |
due to the output not being a regular file. Also split the error message
in any error case here to be on two lines to lessen the likelihood of it
being too long to fit on just one.
|
|
|
|
|
|
|
|
|
|
| |
been extensively tested, but I now can successfully retrieve
<http://www.apache.org/index.html>, so I guess that's a victory of some
sort.
Also move the initialization of ``autherror'' to hopefully eliminate
the reported loop involving authentication. Still need to implement
MD5 digest authentication.
|
|
|
|
| |
that can't deal with a half-closed connection.
|