|-a||Causes snarf to use "active" ftp. By default, snarf uses passive ftp, and, if the server does not support it, falls back to active ftp. Using the -a option will avoid the initial passive attempt.|
|-r||Resumes an interrupted ftp or http transfer by checking if there is a local file with the same name as the remote file, and starting the transfer at the end of the local file and continuing until finished. This option only works with HTTP servers that understand HTTP/1.1 and ftp servers that support the REST command. snarf uses this option automatically if the outfile already exists.|
|-n||Dont resume; ignore the outfile if it exists and re-transfer it in its entirety.|
|-q||Dont print progress bars.|
|-p||Forces printing of progress bars. Snarf has a compile-time option for whether progress bars print by default or not. The -p option overrides the -q option. In addition, if progress bars are enabled by default, snarf suppresses them when standard output is not a terminal. Using -p will override this behavior.|
|-v||Prints all messages that come from the server to stderr.|
|-z||Send a user-agent string similar to what Netscape Navigator 4.0 uses.|
|-m||Send a user-agent string similar to what Microsoft Internet Explorer uses.|
Snarf checks several environment variables when deciding what to use for a proxy. It checks a service-specific variable first, then SNARF_PROXY, then PROXY.
The service-specific variables are HTTP_PROXY, FTP_PROXY, and GOPHER_PROXY.
Snarf also checks the SNARF_HTTP_USER_AGENT environment variable and will use it when reporting its user-agent string to an HTTP server. In the same spirit, it also uses the SNARF_HTTP_REFERER environment variable to spoof a Referer to the web server.
Bugs? What bugs? If you find em, report em.
Copyright (C) 2000 Zachary Beane (email@example.com)
|-->||SNARF (1)||17 Jun 2000|