Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:42840 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 71526 invoked from network); 26 Jan 2009 02:26:21 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 26 Jan 2009 02:26:21 -0000 Authentication-Results: pb1.pair.com header.from=wrowe@rowe-clan.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=wrowe@rowe-clan.net; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain rowe-clan.net from 64.202.165.31 cause and error) X-PHP-List-Original-Sender: wrowe@rowe-clan.net X-Host-Fingerprint: 64.202.165.31 smtpauth18.prod.mesa1.secureserver.net Received: from [64.202.165.31] ([64.202.165.31:57960] helo=smtpauth18.prod.mesa1.secureserver.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B2/73-55096-B4F1D794 for ; Sun, 25 Jan 2009 21:26:20 -0500 Received: (qmail 782 invoked from network); 26 Jan 2009 02:26:16 -0000 Received: from unknown (76.252.112.72) by smtpauth18.prod.mesa1.secureserver.net (64.202.165.31) with ESMTP; 26 Jan 2009 02:26:16 -0000 Message-ID: <497D1F47.2020305@rowe-clan.net> Date: Sun, 25 Jan 2009 20:26:15 -0600 User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 To: Giovanni Giacobbi CC: internals@lists.php.net, dmitry@php.net References: <20090125214352.GA3531@lowca.thgnet.it> <7f3ed2c30901251406i75307f1eh5dd6259d38ed63ce@mail.gmail.com> <20090126011227.GA3825@lowca.thgnet.it> In-Reply-To: <20090126011227.GA3825@lowca.thgnet.it> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Bug in HTTP stream context causes problems in SoapClient/get_sdl() From: wrowe@rowe-clan.net ("William A. Rowe, Jr.") Giovanni Giacobbi wrote: > > @William: I'm not sure I understand your reply: Apache#1 (the one running my test code) has nothing to do in all of this, because PHP is opening a raw socket and communicating on its own with Apache#2 (the one outputting the wsdl with chunked encoding). Thus PHP has to deal with this by itself, you cannot consider it a misconfiguration of Apache#2, because it is legitimately using the HTTP protocol. And further, if the raw socket is processing HTTP/1.1, it must comply with HTTP/1.1 and be willing to accept chunked encoding. Referring to RFC2616, you'll observe it is not optional for either clients nor servers. Thanks for clarifying.