Return-Path: Delivered-To: apmail-httpd-test-dev-archive@httpd.apache.org Received: (qmail 38369 invoked by uid 500); 22 Oct 2001 15:04:08 -0000 Mailing-List: contact test-dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: test-dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list test-dev@httpd.apache.org Received: (qmail 38358 invoked from network); 22 Oct 2001 15:04:08 -0000 Message-ID: <3BD4369E.D79BC60C@Golux.Com> Date: Mon, 22 Oct 2001 11:09:18 -0400 From: Rodent of Unusual Size Organization: The Apache Software Foundation X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Apache test suite Subject: Expectations in apache/404.t Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N H'm. In trying to figure out why apache/404.t was failing test 1 against Apache 1.3, I discovered that it is apparently checking for the HTTP response line: > my $four_oh_four = GET_STR "/404/not/found/test"; > ok ($four_oh_four =~ /HTTP\/1\.[01] Not Found/); Well, GET_STR's result in this case doesn't include the response line, but an analysis of it instead: > RC: 404 (Not Found) > Message: Not Found Where is GET_STR defined, and why does this test pass on some combinations of versions and fail on others? I assume because GET_STR's return semantics have changed.. Anyone see any reason not to change this test to ok (($four_oh_four =~ /HTTP\/1\.[01] Not Found/) || ($four_oh_four =~ /RC:\s+404.*Message:\s+Not Found/s)); ? -- #ken P-)} Ken Coar, Sanagendamgagwedweinini http://Golux.Com/coar/ Author, developer, opinionist http://Apache-Server.Com/ "All right everyone! Step away from the glowing hamburger!"