Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 69178 invoked by uid 500); 20 Nov 2002 22:21:26 -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 69138 invoked from network); 20 Nov 2002 22:21:25 -0000 Date: Wed, 20 Nov 2002 14:21:32 -0800 Subject: Re: Apache 1.3 and invalid headers Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v482) From: "Roy T. Fielding" To: dev@httpd.apache.org Content-Transfer-Encoding: 7bit In-Reply-To: <20021119162933.68561.qmail@web14603.mail.yahoo.com> Message-Id: <6C73CEE4-FCD6-11D6-8D13-000393753936@apache.org> X-Mailer: Apple Mail (2.482) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > Does anyone know what the behaviour of Apache 1.3 is > under the circumstances where the HTTP request or > response contains an invalid request header? > > Specifically, when the Connection header contains > something other than 'close'? There is nothing invalid about that -- connection is completely extensible. > It appears to immediately close the connection - can > anyone confirm or deny that this is Apache's behaviour > for both requests and responses? It does not close the connection on that basis. What you are probably seeing is a server that is configured with keepalive off, in which case all connections are closed regardless of what is received in Connection. ....Roy