Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 47931 invoked by uid 500); 31 Jul 2002 18:55:19 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 47918 invoked from network); 31 Jul 2002 18:55:19 -0000 Message-ID: <3D48353C.78AA9262@Golux.Com> Date: Wed, 31 Jul 2002 15:06:36 -0400 From: Rodent of Unusual Size Organization: The Apache Software Foundation X-Mailer: Mozilla 4.79 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: dev@httpd.apache.org, Waldo Van Cleef Subject: Re: CGI 1.1 Compliance wrt CGI-sent status codes. References: <200207031341.32364.archeron@wavefire.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Waldo Van Cleef wrote: > > Apache 1.3.x breaks the CGI 1.1 specification with its handling of > script-generated status codes. It appears to work in the case of > status 302, but this appearance is only maintained via an > uncoditional redirect in the cast that the "location" header is set > and an OK status exists. Are you sure? I've been using the Status: aspect for years and don't recall seeing anything wrong with it.. -- #ken P-)} Ken Coar, Sanagendamgagwedweinini http://Golux.Com/coar/ Author, developer, opinionist http://Apache-Server.Com/ "Millennium hand and shrimp!"