Received: (from majordom@localhost) by hyperreal.org (8.8.5/8.8.5) id KAA11058; Tue, 1 Jul 1997 10:10:04 -0700 (PDT) Received: (from gnats@localhost) by hyperreal.org (8.8.5/8.8.5) id KAA11046; Tue, 1 Jul 1997 10:10:01 -0700 (PDT) Date: Tue, 1 Jul 1997 10:10:01 -0700 (PDT) Message-Id: <199707011710.KAA11046@hyperreal.org> To: apache-bugdb@apache.org Cc: apache-bugdb@apache.org From: Marc Slemko Subject: Re: general/803: Multiple /// in URLs allowed (e.g. http://host////somefile.html) (fwd) Reply-To: Marc Slemko Sender: apache-bugdb-owner@apache.org Precedence: bulk The following reply was made to PR general/803; it has been noted by GNATS. From: Marc Slemko To: apbugs@apache.org Subject: Re: general/803: Multiple /// in URLs allowed (e.g. http://host////somefile.html) (fwd) Date: Tue, 1 Jul 1997 10:59:37 -0600 (MDT) ---------- Forwarded message ---------- Date: Tue, 01 Jul 1997 10:44:28 +0100 From: Mike Wright To: marc@hyperreal.org Subject: Re: general/803: Multiple /// in URLs allowed (e.g. http://host////somefile.html) marc@hyperreal.org wrote: > > Synopsis: Multiple /// in URLs allowed (e.g. http://host////somefile.html) > > State-Changed-From-To: open-analyzed > State-Changed-By: marc > State-Changed-When: Mon Jun 30 10:55:36 PDT 1997 > State-Changed-Why: > Yes, that is the way Apache behaves, but what is the problem > with it? It is the same behavior as most Unix filesystems > exhibit. Well, that forced me to go look at the definition again, and from the BNF description, /// can occur (http://www.w3.org/Addressing/URL/5_BNF.html). Compliance means no bug. The apache server is relying on the underlying file system which may not act the same way on every system, thus possible inconsistencies. Other servers such as Netscape don't allow multiple /'s in the path (probably to remove the possible inconsistency.) Maybe the apache behavior (even if it's compliant) should be pointed out in the documents. Mike.