Return-Path: owner-new-httpd Received: by taz.hyperreal.com (8.6.10/8.6.5) id GAA25820; Mon, 17 Apr 1995 06:30:44 -0700 Received: from cass41 by taz.hyperreal.com (8.6.10/8.6.5) with SMTP id GAA25814; Mon, 17 Apr 1995 06:30:42 -0700 Received: from cass39.ast.cam.ac.uk by cass41 with smtp (Smail3.1.29.1 #9) id m0s0qse-00004eC; Mon, 17 Apr 95 14:30 BST Received: by cass39.ast.cam.ac.uk (Smail3.1.29.1 #9) id m0s0qsc-0003p9C; Mon, 17 Apr 95 14:30 BST Message-Id: Date: Mon, 17 Apr 95 14:30 BST From: drtr@ast.cam.ac.uk (David Robinson) To: new-httpd@hyperreal.com Subject: Re: indexing suggestion Content-Length: 1264 Sender: owner-new-httpd@apache.org Precedence: bulk Reply-To: new-httpd@apache.org Rst wrote: >...You'd need per-directory DefaultTypes (another potentially useful >extension, though some care would be needed in implementation in the >non-forking case)... This is already available; it is a feature of NCSA httpd 1.3. > Re PATH_INFO; if /dir/file.ext is a regular (unix) file, then accessing > /dir/file.ext/path_info will fail. > >Not currently --- the PATH_INFO is simply ignored in this case. I >personally see no compelling reason to change this, although as we all >will recall, Rob H. vehemently disagrees. However, I do think that >PATH_INFO should clearly be allowed anywhere that a CGI script might >get into the mix. Urgle. I think you did change this with B23. I based my comments on NCSA httpd 1.3, which has the following behaviour: GET /index.html/a HTTP/1.0 returns 403 Forbidden GET /index.html/ HTTP/1.0 returns index.html, but with Content-type: text/plain Whereas for apache 0.5 GET /index.html/a HTTP/1.0 returns index.html GET /index.html/ HTTP/1.0 returns index.html The current apache behaviour is wrong. For /index.html/a it should give 404 Not Found. For /index.html/ it should give 404 Not Found, or perhaps a redirect to /index.html, as in general void path segments are not considered significant. David.