In article <[log in to unmask]>,
Jeff Kell  <[log in to unmask]> wrote:
>An earlier post (sorry, I zapped it and can't quote it) alluded to the fact
>that given a fully qualified URL, e.g., http://www.company.com, that you
>only had to provide Netscape with "company.com".  Not 100% correct.
>
>It WILL infer the "http://" but does NOT (Netscape 2.0 32-bit Windows 95)
>make inferences on the "www." part.
 
Right.  From the 2.0 release notes:
 
Less typing to access FTP and Gopher: If the hostname is ftp or
gopher, you don't have to specify the protocol identifier when
entering a URL into the location field. For hostnames other than ftp
or gopher, the Navigator will default to http. For example, entering:
      ftp.netscape.com takes you to ftp://ftp.netscape.com/
 
If you have an http server named ftp or gopher, you can still get to
it by typing the protocol identifier. For example:
      http://gopher.netscape.com/