Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:29125 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 17446 invoked by uid 1010); 1 May 2007 11:16:35 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 17431 invoked from network); 1 May 2007 11:16:35 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 1 May 2007 11:16:35 -0000 Authentication-Results: pb1.pair.com smtp.mail=lists@block-online.eu; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=lists@block-online.eu; sender-id=unknown Received-SPF: error (pb1.pair.com: domain block-online.eu from 81.169.146.160 cause and error) X-PHP-List-Original-Sender: lists@block-online.eu X-Host-Fingerprint: 81.169.146.160 mo-p00-ob.rzone.de Solaris 10 (beta) Received: from [81.169.146.160] ([81.169.146.160:25811] helo=mo-p00-ob.rzone.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id DE/47-40722-A8127364 for ; Tue, 01 May 2007 07:16:28 -0400 Received: from ollie.block.home ([84.63.182.58] [84.63.182.58]) by post.webmailer.de (mrclete mo14) (RZmta 5.8) with ESMTP id B04a80j417sFkw for ; Tue, 1 May 2007 13:16:23 +0200 (MEST) To: internals@lists.php.net Date: Tue, 1 May 2007 13:15:05 +0200 User-Agent: KMail/1.7.1 References: <200705010212.52622.lists@block-online.eu> <4636883E.7010603@lerdorf.com> In-Reply-To: <4636883E.7010603@lerdorf.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-ID: <200705011315.06066.lists@block-online.eu> X-RZG-AUTH: jsAgD75E4FZRsMYse5W8COLJ40bV42cELvihCND/Uu2brXmKBiVoj4QKsiU= X-RZG-CLASS-ID: mo00 Subject: Re: [PHP-DEV] Setting HTTP results code vs. HTTP type From: lists@block-online.eu (Oliver Block) Am Dienstag, 1. Mai 2007 02:22 schrieb Rasmus Lerdorf: > Oliver Block wrote: > 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. Well. Regards, Oliver