On Tuesday 15 January 2002 14:36 pm, Amarendra Godbole (Intl Vendor) wrote: > > How? Please explain. The slashless version should be > > preferred in case of some misconfigured http servers, IMO. > > I _assume_ a properly configured http server. ;)
Still you haven't explained how typing http://gcc.gnu.org or http://gcc.gnu.org/ into the browser window makes a difference in network traffic. I tried with lynx and in both cases the request that went was (I have removed the Accept: headers, since they were too long) GET / HTTP/1.0 Host: gcc.gnu.org Accept-Encoding: gzip, compress Accept-Language: en User-Agent: Lynx/2.8.4rel.1 libwww-FM/2.14 SSL-MM/1.4.1 OpenSSL/0.9.6b If you give a path after the site name (www.somesite.com/somedir, for example) then with some webservers the slash might matter if somedir is a directory. This might generate a HTTP 30x server response, but I don't think the excess traffic is of any consequence. Binand _______________________________________________ linux-india-help mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/linux-india-help
