ChunkedBody decoding with Curl Adapter
Opened this issue · 7 comments
Zend\Http\Response::decodeChunkedBody fail with exception when curl adapter decode body itself , BUT it still has "Transfer-Encoding: encoded" header
$client = new \Zend\Http\Client();
$client->setOptions(array(
'sslverifypeer' => false,
'adapter' => 'Zend\Http\Client\Adapter\Curl',
));
$client->setUri('https://www.truesocialmetrics.com/');
$response = $client->send(); // Error parsing body - doesn't seem to be a chunked message
php: 5.5 , 5.6, 7
It looks like you're leaving off the $response->getBody() call that would actually cause the exception.
At any rate, in this case, it looks like the problem is that the server you're talking to sends the header in lowercase: transfer-encoding: chunked, while the code in the curl adapter that's supposed to deal with this (line 437) only looks for the uppercase version.
Header names are case-insensitive by definition, and the values for Transfer-Encoding are also case-insensitive, so just adding the i case-insensitivity flag to the regex being used here is probably a reasonable solution.
This would be fixed by the open PR #10, and this issue serves as an example of the kind of bug that currently happens and that PR would fix.
Specifically, this looks like a regression introduced by ddf5a83: the comparisons were case-sensitive at that point, and when adding support for varying whitespace, the insensitivity was accidentally not applied to the new regex version of the code.
Any idea when this would be fixed?
Nope. I've patched zend to solve this issue.
Who is the current maintainer of Zend\Http?
I suppose that's @weierophinney
This repository has been closed and moved to laminas/laminas-http; a new issue has been opened at laminas/laminas-http#25.