Description: ------------ Fetching http://schou.dk/ via HTTP GET fails because of HTTP_Request2_MessageException: Cannot decode chunked response, invalid chunk length '' Test script: --------------- <?php require 'HTTP/Request2.php'; $req = new HTTP_Request2(); $req->setUrl('http://schou.dk/'); $req->send(); ?> Expected result: ---------------- no error. Browsers can show the page without problems. Actual result: -------------- PHP Fatal error: Uncaught HTTP_Request2_MessageException: Cannot decode chunked response, invalid chunk length '' in /usr/share/php/HTTP/Request2/Adapter/Socket.php on line 1056 #0 /usr/share/php/HTTP/Request2/Adapter/Socket.php(1056): HTTP_Request2_Adapter_Socket->readChunked(16384) #1 /usr/share/php/HTTP/Request2/Adapter/Socket.php(136): HTTP_Request2_Adapter_Socket->readResponse() #2 /usr/share/php/HTTP/Request2.php(939): HTTP_Request2_Adapter_Socket->sendRequest(Object(HTTP_Request2)) #3 /home/cweiske/Dev/pear/test-http_request2-schou.php(5): HTTP_Request2->send() #4 {main} thrown in /usr/share/php/HTTP/Request2/Adapter/Socket.php on line 1099

I have the same bug "Cannot decode chunked response, invalid chunk length" like Christian Weiske mentions. Any idea for this issue?

I found by myself that wampserver with apache 2.4.2 has some problems. Just change version of apache to 2.4.2 by installing another version of wampserver and everything works well. Thanks.

The http://schou.dk/ site sends invalid chunked response that does not contain last-chunk as described in http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.6.1 This can probably be handled without an exception, though, just reading the response until eof

For the record: the site in question reports Apache 2.2.22, so this is most probably a known bug in mod_proxy https://www.apachelounge.com/viewtopic.php?t=3552 Another thing to consider is that console curl outputs error 18 (CURLE_PARTIAL_FILE) if trying to access that site, curl_exec() in Curl Adapter returns the data, but curl_errno() on handle also returns error 18. Perhaps a means to add warnings to HTTP_Request2_Response should be devised for situations like this where a "hard" Exception is a bit too much. Or maybe a 'warning' event for Observers?

Fixed in Git: https://github.com/pear/HTTP_Request2/commit/10edbc9d8e3aeec60c55dd241313174c173ea440 Also a new 'warning' event is dispatched to Observers if incomplete body was received.