Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:29126 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 19494 invoked by uid 1010); 1 May 2007 11:22:17 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 19479 invoked from network); 1 May 2007 11:22:17 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 May 2007 11:22:17 -0000 Authentication-Results: pb1.pair.com header.from=thetaphi@php.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=thetaphi@php.net; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain php.net from 80.190.230.99 cause and error) X-PHP-List-Original-Sender: thetaphi@php.net X-Host-Fingerprint: 80.190.230.99 www.troja.net Linux 2.5 (sometimes 2.4) (4) Received: from [80.190.230.99] ([80.190.230.99:42925] helo=mail.troja.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 62/97-40722-8E227364 for ; Tue, 01 May 2007 07:22:17 -0400 Received: from localhost (localhost [127.0.0.1]) by mail.troja.net (Postfix) with ESMTP id 2B1D2297F8; Tue, 1 May 2007 13:22:34 +0200 (CEST) Received: from mail.troja.net ([127.0.0.1]) by localhost (cyca.troja.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 31714-04; Tue, 1 May 2007 13:22:32 +0200 (CEST) Received: from VEGA (port-83-236-62-78.dynamic.qsc.de [83.236.62.78]) (using SSLv3 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.troja.net (Postfix) with ESMTP id D6EAB29781; Tue, 1 May 2007 13:22:31 +0200 (CEST) To: "'Rasmus Lerdorf'" , "'Oliver Block'" Cc: References: <46367F96.6080205@cschneid.com> <46368091.4050606@lerdorf.com> <200705010212.52622.lists@block-online.eu> <4636883E.7010603@lerdorf.com> Date: Tue, 1 May 2007 13:22:13 +0200 Message-ID: <000c01c78be2$f7c91a10$0201a8c0@VEGA> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <4636883E.7010603@lerdorf.com> Thread-Index: AceLhu9MV2Wcup5nTW+RhgrY+7aEVgAW5VUg X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 X-Virus-Scanned: amavisd-new at troja.net Subject: RE: [PHP-DEV] Setting HTTP results code vs. HTTP type From: thetaphi@php.net ("Uwe Schindler") > -----Original Message----- > From: Rasmus Lerdorf [mailto:rasmus@lerdorf.com] > Sent: Tuesday, May 01, 2007 2:22 AM > To: Oliver Block > Cc: internals@lists.php.net > Subject: Re: [PHP-DEV] Setting HTTP results code vs. HTTP type > > Oliver Block wrote: > > Am Dienstag, 1. Mai 2007 01:49 schrieb Rasmus Lerdorf: > > > >> This came up many times on the Apache lists years ago, and Roy Fielding > >> who wrote that spec repeatedly said it was fine to reply with a 1.1 > >> response to a 1.0 request. > > > > Did he give any rationale for his view? > > Go read the archives. And note that I only said it was fine to respond > with a 1.1 reply, that doesn't mean it is fine to send an encoding the > client doesn't support. And that's exactly what other web servers also do: I come from Sun One Web Server 6.1 and 7.0), so I can tell what they do: They respond always with HTTP/1.1 but if the request came in with HTTP/1.0 they do not use chunked encoding for the reply and use "Connection: close". Uwe