Perl scripts and HTML files are ASCII files, along with many others. If you use a plain text editor to work with a file, it's an ASCII file. It's not terribly important to transfer HTML files in ASCII mode, but it is important for Perl scripts.
GIFs and JPEGs are binary files. They must be uploaded in binary mode, or will be corrupted. Files that look like garbage in a plain text editor and require a more advanced program to edit are not ASCII files, and must be transferred in binary mode.
Internet providers such as AOL, CompuServe, and Prodigy may have a built-in FTP interface. If you have a PPP internet account and need an FTP program, you can download software for for either the PC or Mac. We suggest that you contact your local internet provider to inquire about compatibility. Microsoft FrontPage users whom have had extensions installed within their web site should use FrontPage to transfer files only.
Each time you run WS_FTP the Session Profile window will be displayed.
A profile contains the information needed to connect to your web site.
Creating a profile now will eliminate the need for you to configure the
software each time you wish to connect to the web server via FTP. To create
a new profile, click the "New" button and enter a generic profile name
at the top of the Session Profile window. Next, enter the userid, password
and hostname for your web site.
Be sure to select "Auto detect" for the Host Type. (see Fig.1) It is
best to select "Save Password" and "Auto Save Config" to maintain these
settings for future use. All other fields can be left blank. You are now
ready to connect to the web server. Click "Ok" to continue.
As soon as a file is uploaded to the web server, it is available for all to see. If, after uploading a file, you are still unable to see the updated file via Netscape, you need to clear both disk and browser cache. This function can be found by selecting Options > Network Preferences in Netscape. Remember that you must first be connected to the internet through your local internet service provider in order to connect to the web server.
ASCII files (text)
Type ascii to make sure you are in ascii mode.
Type put filename to put a file.
Type get filename to get a file.
Binary files (graphics)
Type binary to make sure you are in binary mode.
Type put filename to put a file.
Type get filename to get a file.
Multiple files: type prompt and be sure the message you get says something like 'prompting disabled'. (Not necessary, but certainly nice when doing a lot of files.) Then, type mget *gif to get all the files ending in gif or mget sausage* to get all the files starting with sausage. There is also an mput command for doing the same thing in the other direction.
Once logged on, you may use the following commands (assuming your telnet program knows or can be taught about ZMODEM, which often isn't the case):
ASCII files (text)
Type rz to put a file.
Type sz -a filename to get a file.
Binary files (graphics)
Type rz filename to put a file.
Type sz -b filename to get a file.
Once logged on, you may use the same commands listed in the last section.
So why this section? If this seems obvious, sorry, but probably the single biggest type of problem we have to correct or tell users to do over is problems caused by having the wrong mode active. We needed this in big letters so you'd find it.
Macintosh users: in Fetch, the binary mode referred to throughout the manual is 'raw'. The other option uploads too much data, corrupting the file. ASCII mode is 'text'.
In case you're wondering what the fuss is about -- aren't text files standardized? -- here's the explanation. While ASCII is a standard for encoding text, it does not specify how to end lines. There are two obvious candidates in the ASCII character set: CR and LF. (Carriage Return and Line Feed.) *nix machines, such as the Web 66 WWW machines, use LF to terminate lines. Macintoshes use CR. DOS, Windows, and NT machines use CR LF (both, in that order). When transferring files between machines of different types, you need to account for this, hence ASCII mode. To avoid damaging binary files (where the bytes don't have the ASCII semantics) there is binary mode.