On 01/05/2008 03:54 PM, Jim Jagielski wrote:
>> 2. Excerpt from first test results: >> >> >> 1\r\n >> \r\r\n >> e\r\n >> 1\r\n >> z\r\n >> 1\r\n >> m\r\n >> 1\r\r\n >> 0\r\n >> \r\n >> >> >> This an invalid chunked encoding (\r is already the one byte that was >> announced for this >> chunk. e\r\n would need to have 1\r\n in front). >> This is very strange as the ap_http_filter dechunks the results from >> backend and >> ap_http_chunk_filter creates a new chunked encoding. I have to correct myself a little bit. I read this from the beginning which indicates wrong chunked encoding. In fact it has to read from the back so we end up with 1\r\n \r\r\n e\r\n 1\r\n z\r\n 1\r\n m\r\n 1\r\r\n 0\r\n \r\n Formating this chunklength\r\n content \r\n results in 1\r\n \r \r\n e\r\n 1\r\nz\r\n1\r\nm\r\n1\r \r\n 0\r\n \r\n which would be correct. Regards Rüdiger
