From owner-freebsd-current Wed Feb 25 05:37:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA10216 for freebsd-current-outgoing; Wed, 25 Feb 1998 05:37:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tyree.iii.co.uk ([195.89.149.230]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA10211 for ; Wed, 25 Feb 1998 05:37:12 -0800 (PST) (envelope-from nik@iii.co.uk) From: nik@iii.co.uk Received: from carrig.strand.iii.co.uk (carrig.strand.iii.co.uk [192.168.7.25]) by tyree.iii.co.uk (8.8.8/8.8.8) with ESMTP id KAA09965; Wed, 25 Feb 1998 10:16:36 GMT Received: (from nik@localhost) by carrig.strand.iii.co.uk (8.8.7/8.8.7) id KAA03000; Wed, 25 Feb 1998 10:21:53 GMT Message-ID: <19980225102152.50924@iii.co.uk> Date: Wed, 25 Feb 1998 10:21:53 +0000 To: Terry Lambert Cc: current@FreeBSD.ORG Subject: Re: DEVFS/SLICE and SOFT UPDATE patches. References: <34F378E8.2781E494@whistle.com> <199802250252.TAA10749@usr04.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.85e In-Reply-To: <199802250252.TAA10749@usr04.primenet.com>; from Terry Lambert on Wed, Feb 25, 1998 at 02:52:23AM +0000 Organization: interactive investor Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Feb 25, 1998 at 02:52:23AM +0000, Terry Lambert wrote: > Use http://www.freebsd.org/~julian/ if you are using a brain-damaged > browser. For some reason, the trailing "/" is important to the WWW > server on FreeeBSD.org... > > This is a job for... Variant Symbolic Links! Uh, no it isn't. It's a job for people to start writing URLs properly. If you're referring to a directory (as the URL above is) then you must include the trailing slash. Otherwise, the webserver thinks you're trying to retrieve a file of that name instead. When the web server realises that the file is not there, it will either a) Return the appropriate "File not found" code to the browser or b) Speculatively put a '/' on the end and try again. I don't think any web servers currently do (b), but I wouldn't stake my life on it. When a server responds with (a) the browser may or may not speculatively put a '/' on the end and resubmit the request. Most browsers do indeed do this. Some obviously don't, and I presume these are the 'brain damaged ones' referred to above. The overall effect is to contribute to the general slow down of the 'net, since your browser is submitting two requests to the server. Network traffic increases, browser logs are artificially inflated, servers that speculatively spawn multiple children to handle 'n' requests will kill those children earlier when they've done less useful work, and so on. We now return you to your "Ethernet vs. Token Ring" discussion. . . N -- --+==[ Nik Clayton is Just Another Perl Hacker at Interactive Investor ]==+-- . . . and relax To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message