Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:43707
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 63.205.162.116 as permitted sender)
Message-ID: <49E51FF2.4010609@zend.com>
Date: Tue, 14 Apr 2009 16:44:50 -0700
Organization: Zend Technologies
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: Dmitry Stogov <dmitry@zend.com>
CC: PHP Internals <internals@lists.php.net>, 
 Lukas Kahwe Smith <mls@pooteeweet.org>,
 =?ISO-8859-1?Q?Johannes_Schl=FCter?= <johannes@php.net>, 
 Andi Gutmans <andi@zend.com>,
 Sara Golemon <pollita@php.net>
References: <49E4A4CD.5010809@zend.com>
In-Reply-To: <49E4A4CD.5010809@zend.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: Support for "Transfer-Encoding: chunked" in http stream wrapper
From: stas@zend.com (Stanislav Malyshev)

Hi!

> The attached patch implements automatic decoding of chunked 
> transfer-encoding.

 From what I see in the patch, it requires chunked data prefix to be:

XXX\r\n

where XXX are from 1 to 3 hex digits. However RFC 2616 defines chunk 
size as arbitrarily long sequence of HEX digits, and also allows for 
some stuff (extensions) to be added to the end. I wonder if it'd be 
better to treat all hex digits as size and then ignore everything until 
\r\n.

Also, I understand that by the RFC chunked encoding should never be sent 
to HTTP/1.0 clients. So, by default this should never happen unless you 
manually set protocol version to 1.1 (or the server is broken).

-- 
Stanislav Malyshev, Zend Software Architect
stas@zend.com   http://www.zend.com/
(408)253-8829   MSN: stas@zend.com