Hi All,
Because PHP 5.3.x does not handle HTTP 1.1 chunked encoding properly, we've updated the PHP Google Ads client library to use HTTP 1.0 for PHP 5.3.x. You can download the updated client library from GitHub<https://github.com/googleads/googleads-php-lib> . PHP 5.2 users take note: We are unable to force HTTP 1.0 protocol in PHP 5.2.x. PHP 5.2 has been unsupported for more than 3 years<http://php.net/eol.php>. We recommend you upgrade to a current PHP version<http://us3.php.net/downloads.php>as soon as possible to avoid future interruptions. Thanks, Ray Tsang - AdWords API Advisor On Friday, March 21, 2014 6:33:58 PM UTC-4, Ray Tsang (AdWords API Team) wrote: > > Hi All, > > We’ve identified the cause for this issue. The fix has been deployed and > your requests should continue to work now. > > Longer Answer: > > There was a recent server change to utilize the HTTP 1.1 chunked transfer > encoding. This change affected some of the PHP platform versions that > cannot properly handle HTTP 1.1 protocol with respect to chunked transfer. > > This inadvertently affects any applications/libraries using those older > PHP versions, which includes the Ads PHP client library as well. > > We’ve removed chunked transfer encoding from the server side. Your > requests should continue to work now. Your previous requests that resulted > “Error Fetching http body, No Content-Length, connection closed or > chunked data” errors were processed by the AdWords API servers, but the > SOAP response could not be decoded due to the aforementioned issue related > to the some of the older PHP versions. > > As far as we know, PHP 5.4 is the only version that’s completely > unaffected. All PHP 5.2 users are recommended to upgrade since PHP 5.2 has > been end-of-life for more than 3 years <http://php.net/eol.php>. > > We are also working on a client library update to force HTTP 1.0 protocol > if you are using an affected PHP version. Please lookout for an update on > this thread when the library is ready. > > Cheers, > > Ray Tsang - AdWords API Advisor > > On Friday, March 21, 2014 2:24:01 PM UTC-4, Rob Rudnicki wrote: >> >> for those looking at this thread for updates. The issues seems to have >> been resolved. I had the issue earlier but no longer. >> > -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
