Return-Path: Delivered-To: apmail-httpd-apreq-dev-archive@httpd.apache.org Received: (qmail 31077 invoked by uid 500); 14 Apr 2003 03:59:42 -0000 Mailing-List: contact apreq-dev-help@httpd.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Delivered-To: mailing list apreq-dev@httpd.apache.org Received: (qmail 30965 invoked from network); 14 Apr 2003 03:59:42 -0000 Received: from theoryx5.uwinnipeg.ca (142.132.1.82) by daedalus.apache.org with SMTP; 14 Apr 2003 03:59:42 -0000 Received: from localhost (randy@localhost) by theoryx5.uwinnipeg.ca (8.11.6/8.11.6) with ESMTP id h3E3mvZ06092; Sun, 13 Apr 2003 22:48:57 -0500 Date: Sun, 13 Apr 2003 22:48:57 -0500 (CDT) From: Randy Kobes To: Stas Bekman cc: Joe Schaefer , , Subject: Re: [win32] Locations in Apache-Test framework In-Reply-To: <3E9A2E7F.4050505@stason.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Mon, 14 Apr 2003, Stas Bekman wrote: > Randy Kobes wrote: > > On Mon, 14 Apr 2003, Stas Bekman wrote: > > > > [ .. ] > > > >>Randy, what happens if you configure some valid virtual > >>resource as foo::bar (outside of Apache::Test) and try > >>accessing it? Do you get 403? > > > > Yes I do, with both apache-1.3.27 and httpd-2.0.45 - a > > working > > > > SetHandler perl-script > > PerlHandler Apache::Hello > > > > (PerlResponseHandler for modperl 2) generates a 403 by simply > > changing this to, eg, . For some reason the > > modperl 2 tests don't run into this problem - I'll try to see > > why. > > Could it be due to this handler, running for all requests? > > PerlTransHandler TestHooks::trans > > May be after calling $r->uri, Apache initializes some data structure, which > doesn't cause a latter problem? You're good at this stuff :) Commenting out the PerlTransHandler in httpd.conf in the mod_perl 2 tests does lead to the 403 errors in tests that successfully run with PerlTransHandler. > > Actually, again on both 1.3.x and 2.0.45, making a request for > > http://localhost/foo::bar (where foo::bar doesn't appear in a > > ) generates a 403, rather than a 404. > > Randy, can you please run this by httpd-dev? This doesn't seem right. > > (Certainly we still want to be able to run tests on winFU, but let's first > figure out why this thing happens). I'll do that - I looked for a bug report for this earlier, but couldn't find one. And just in case it was some quirk of my system, I tried this on f3.freespace.jp, which netcraft reports as running Apache/1.3.27 on Win32 - a request there for some (presumably) non-existent thing results in a 403 if that thing has a ':' in it. -- best regards, randy