Ошибка error fetching http headers

I have been getting Error fetching http headers for two reasons:

1. The server takes to long time to answer.
2. The server does not support Keep-Alive connections (which my answer covers).

PHP will always try to use a persistent connection to the web service by sending the Connection: Keep-Alive HTTP header. If the server always closes the connection and has not done so (PHP has not received EOF), you can get Error fetching http headers when PHP tries to reuse the connection that is already closed on the server side.

Note: this scenario will only happen if the same SoapClient object sends more than one request and with a high frequency. Sending Connection: close HTTP header along with the first request would have fixed this.

In PHP version 5.3.5 (currently delivered with Ubuntu) setting the HTTP header Connection: Close is not supported by SoapClient. One should be able to send in the HTTP header in a stream context (using the $option — key stream_context as argument to SoapClient), but SoapClient does not support changing the Connection header (Update: This bug was solved in PHP version 5.3.11).

An other solution is to implement your own __doRequest(). On the link provided, a guy uses Curl to send the request. This will make your PHP application dependent on Curl. The implementation is also missing functionality like saving request/response headers.

A third solution is to just close the connection just after the response is received. This can be done by setting SoapClients attribute httpsocket to NULL in __doRequest(), __call() or __soapCall(). Example with __call():

class MySoapClient extends SoapClient {
    function __call ($function_name , $arguments) {
        $response = parent::__call ($function_name , $arguments);
        $this->httpsocket = NULL;
        return $response;
    }
}

Answer by Salvatore Hansen

I know this won’t be the answer to everyone’s problem, but hopefully it helps someone. Either way I think it’s important to realise that the cause of this error (faultcode: «HTTP» faultstring: «Error Fetching http headers») is usually going to be a network/socket/protocol/communication issue rather than simply «not allowing enough time for the request». I can’t imagine expanding the default_socket_timeout value is going to resolve this problem very often, and even if it does, surely it would be better to resolve the issue of WHY it is so slow in the first place.,The SoapClient expects the SOAP envelope but receives a HTML code.
That’s why PHP responds with: «Error Fetching Http Headers» because it can not understand what he received in response. To resolve the problem, contact your network administrator to verify if there is any Firewall, NAT or proxy getting in the way and then ask them to make the necessary arrangements.,During my tests I have defined the default_socket_timeout to 5 seconds and the error ‘Error Fetching http headers’ was raised instantaneously.,It turned out that the misbehaving soap servers sent a HTTP-header with every response which lead to the soap client choking on the second soap call:
Connection: Upgrade, close. The well-behaving servers did not send a Upgrade on successive responses.

You can increase it like so:

ini_set('default_socket_timeout', 600); // or whatever new value you want

Answer by Regina Burns

This error is often seen when the default_socket_timeout value is exceeded for the SOAP response. ,Note from the SoapClient constructor: the connection_timeout option is used for defining a timeout value for connecting to the service, not for the timeout for its response., Error fetching http headers in SoapClient ,I’ve found that increasing default_socket_timeout in php.ini should fix it, but it did not work.

I’m trying to invoke a WS over https on a remote host:remote port and I get:

Error fetching http headers

 Here is the code:

$wsdl="myWSDL";

$client = new SoapClient($wsdl,array('connection_timeout'=>5,'trace'=>true,'soap_version'=>SOAP_1_2));

var_dump($client->__getFunctions());

try {
    $response=$client->myFunction("1","2","3");
         } catch (SoapFault $fault) {
    var_dump($fault);
    }
}

Answer by Ronan Knight

This error can appear on the client if there is a problem on the server side. For example, if the SOAP server is a PHP script with a parse error, the client will fail with this message.,Now refresh the client and watch for the error message. Any PHP errors with the server script will be shown.,The Contents are licensed under creative commons.,This whole game of headers that we are passing. I solved my problem with adding the compression header property. This actually require when you are expecting response in gzip compressed format.

I’m trying to create a soap connection to Magento’s web services, however I’m getting an error when I try and create an instance of the soap client class. I can view the wsdl file in firefox without problems and I can watch php make the request for the wsdl in apaches logs but it still fails. Nusoap can connect.

$proxy = new SoapClient('someaddress?wsdl');

The error is

<b>Fatal error</b>:  Uncaught SoapFault exception: [HTTP] Error Fetching http headers in /home/sites/xxx/xxx_main/system/application/views/contentpage_templates/gift_service.php:29
Stack trace:
[internal function]: SoapClient-&gt;__doRequest('&lt;?xml version=&quot;...',    'http://cornishw...', 'urn:Mage_Api_Mo...', 1, 0)
[internal function]: SoapClient-&gt;__call('call', Array)
/home/sites/xxx/xxx_main/system/application/views/contentpage_templates/gift_service.php(29): SoapClient-&gt;call(NULL, 'catalog_categor...', 5, 'giftshop')
/home/sites/xxx/xxx_main/system/application/libraries/MY_Loader.php(586): include('/home/sites/cor...')
/home/sites/xxx/xxx_main/system/application/libraries/MY_Loader.php(228): MY_Loader-&gt;_ci_load(Array, '')
/home/sites/xxx/xxx_main/system/application/modules/contentpage/controllers/contentpage.php(44): MY_Loader-&gt;view('contentpage_tem...', false, true)
[internal function]: Contentpage-&gt;index()
/home/sites/xxx in <b>/home/sites/xxx/xxx_main/system/application/views/contentpage_templates/gift_service.php</b> on line <b>29</b>

Answer by Blaze Weaver

When this error is encountered, there are three common solutions to head off the error by remedying either the timeout directly or how the API returns the results.,»Error Fetching http headers» is a common error to encounter when working with the SLAPI. Fortunately, it is not terribly difficult to avoid. This error most commonly met when working with a large sets of data and can be a bit cryptic, as it seems to imply some sort of connection issue. In truth, it is a client side error provided when a timeout occurs while waiting for a response from the API.,This varies depending on what client you are using to communicate with the SLAPI, but increasing your timeout limit to several minutes may help. Re-trying the request itself might also work. This is the easiest solution, but also the least likely to work long term.,
If this article contains any error, or leaves any of your questions unanswered, please help us out by
opening up a github issue.
Open an issue

"Error Fetching http headers" is a common error to encounter when working with the SLAPI. Fortunately, it is not terribly difficult to avoid. This error most commonly met when working with a large sets of data and can be a bit cryptic, as it seems to imply some sort of connection issue. In truth, it is a client side error provided when a timeout occurs while waiting for a response from the API.

"Error Fetching http headers"

Answer by Alia Escobar

Has this issue been resolved at your end? Or was it closed by accident?,

Sorry, something went wrong.
,
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
,Successfully merging a pull request may close this issue.

		$reportQuery->setDimensions([
			Dimension::DATE,
			Dimension::ADVERTISER_NAME,
			Dimension::LINE_ITEM_NAME,
			Dimension::AD_UNIT_NAME,
			Dimension::MASTER_COMPANION_CREATIVE_NAME
			]);

		$reportQuery->setColumns([
			Column::TOTAL_LINE_ITEM_LEVEL_IMPRESSIONS,
			Column::TOTAL_LINE_ITEM_LEVEL_CLICKS,
			Column::TOTAL_ACTIVE_VIEW_VIEWABLE_IMPRESSIONS,
			Column::TOTAL_ACTIVE_VIEW_MEASURABLE_IMPRESSIONS,
			Column::TOTAL_ACTIVE_VIEW_VIEWABLE_IMPRESSIONS_RATE,
			Column::TOTAL_ACTIVE_VIEW_ELIGIBLE_IMPRESSIONS,
			Column::TOTAL_ACTIVE_VIEW_MEASURABLE_IMPRESSIONS_RATE
			]);

		$reportQuery->setAdUnitView(ReportQueryAdUnitView::HIERARCHICAL);
		$reportQuery->setDateRangeType(DateRangeType::CUSTOM_DATE);
		$reportQuery->setStartDate(DfpDateTimes::fromDateTime(
			new DateTime('-4 days', new DateTimeZone('America/Phoenix')))->getDate());
		$reportQuery->setEndDate(DfpDateTimes::fromDateTime(
			new DateTime('now', new DateTimeZone('America/Phoenix')))->getDate());

		$this->logProgress('Creating a new Report Job.');
		$reportJob = new ReportJob();

		$reportJob->setReportQuery($reportQuery);`

Answer by Sadie Navarro

We use bingads PHP lib. Sometimes, when we try to make a call using GetCampaignCriterionsByIds or AddCampaignCriterions methods we get «Error Fetching http headers» but when repeat call we get success. Why does it happen? What does this error mean exactly?,The error seems not specific to the Bing Ads API. ,Where to place Bing API Code in Shopify,This error also repeats randomly by calling other API methods.

So this isn’t a solution to the problem, but it’s a work around that’s working for me:

 $failed = false;
 do {
     try {
         $poll_response = $this->ServiceClient->GetService()->PollGenerateReport($request);
         $failed = false;
     }
     catch(Exception $e) {
         $failed = true;
     }
 } while ($failed);

Answer by Lawson Graves

[2008-09-12 07:49 UTC] filip_stjernberg at hotmaol dot com

Description:
------------
I'm trying to use an existing webservice:
http://testhorizon.gothiagroup.com/AFSServices/AFSService.svc?wsdl

There is a simple test function called "HelloWorld" that returns the input "myVaule". This function dos not need authentification but its more advaced one do.

Really need this to work, have tried nuSOAP to but that gives me other problems.

Reproduce code:
---------------
This is the code I use:

try{
    $wsdl = 'http://testhorizon.gothiagroup.com/AFSServices/AFSService.svc?wsdl';
    $client = new SoapClient($wsdl,
    array(
          'soap_version' => SOAP_1_2,
          'trace'      => 1,
          'exceptions' => 1
    ));

    print($client->HelloWorld(array('myValue' => 'Test')));
    
} catch (Exception $e) {
    printf("Message = %sn",$e->__toString());
}

print "<pre>n";
  print "Request :n".htmlspecialchars($client->__getLastRequest()) ."n";
  print "Response:n".htmlspecialchars($client->__getLastResponse())."n";
  print "</pre>";

Expected result:
----------------
Hello from AFSService: Test

Actual result:
--------------
Message = SoapFault exception: [HTTP] Error Fetching http headers in /customers/veus.se/veus.se/httpd.www/Test/samples/AFSWS1.php:20 Stack trace: #0 [internal function]: SoapClient->__doRequest('<?xml version="...', 'http://testhori...', 'http://tempuri....', 2, 0) #1 [internal function]: SoapClient->__call('HelloWorld', Array) #2 /customers/veus.se/veus.se/httpd.www/Test/samples/AFSWS1.php(20): SoapClient->HelloWorld(Array) #3 {main} 

nRequest :n<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope" xmlns:ns1="http://tempuri.org/"><env:Body><ns1:HelloWorld><ns1:myValue>Exor</ns1:myValue></ns1:HelloWorld></env:Body></env:Envelope>

nResponse:nn

Solution 1

This error is often seen when the default_socket_timeout value is exceeded for the SOAP response. (See this link.)

Note from the SoapClient constructor: the connection_timeout option is used for defining a timeout value for connecting to the service, not for the timeout for its response.

You can increase it like so:

ini_set('default_socket_timeout', 600); // or whatever new value you want

This should tell you if the timeout is the issue, or whether you have a different problem. Bear in mind that you should not use this as a permanent solution, but rather to see if it gets rid of the error before moving on to investigate why the SOAP service is responding so slowly. If the service is consistently this slow, you may have to consider offline/batch processing.

Solution 2

Just wanted to share the solution to this problem in my specific situation (I had identical symptoms). In my scenario it turned out to be that the ssl certificate provided by the web service was no longer trusted. It actually turned out to be due to a new firewall that the client had installed which was interfering with the SOAP request, but the end result was that the certificate was not being correctly served/trusted.

It was a bit difficult to track down because the SoapClient call (even with trace=1) doesn’t give very helpful feedback.

I was able to prove the untrusted certificate by using:

openssl s_client -connect <web service host>:<port>

I know this won’t be the answer to everyone’s problem, but hopefully it helps someone. Either way I think it’s important to realise that the cause of this error (faultcode: «HTTP» faultstring: «Error Fetching http headers») is usually going to be a network/socket/protocol/communication issue rather than simply «not allowing enough time for the request». I can’t imagine expanding the default_socket_timeout value is going to resolve this problem very often, and even if it does, surely it would be better to resolve the issue of WHY it is so slow in the first place.

Solution 3

I faced same problem and tried all the above solutions. Sadly nothing worked.

1. Socket Timeout (Didn’t work)
2. User Agent (Didn’t work)
3. SoapClient configuration, cache_wsdl and Keep-Alive etc…

I solved my problem with adding the compression header property. This is actually required when you are expecting a response in gzip compressed format.

//set the Headers of Soap Client. 
$client = new SoapClient($wsdlUrl, array(
    'trace' => true, 
    'keep_alive' => true,
    'connection_timeout' => 5000,
    'cache_wsdl' => WSDL_CACHE_NONE,
    'compression'   => SOAP_COMPRESSION_ACCEPT | SOAP_COMPRESSION_GZIP | SOAP_COMPRESSION_DEFLATE,
));

Hope it helps.

Good luck.

new SoapClient($api_url, array('keep_alive' => false));

Добрый день.
есть такой код:

$client = new SoapClient("http://region.4sides.ru:6612/PiligrimServises.svc?wsdl", array('trace' => 1));
$data = $client->DepartureInfo(array("BarCod" => $barcod));

собственно он и выкидывает ошибку такого формата
SoapFault: Error Fetching http headers в функции SoapClient->__doRequest()

подскажите пожалуйста, в какую сторону копать?