I had a similar problem a long time ago. Not related to this plug-in.
Almost the exact same error message : "SoapFault Object ( [message:blahdeeblah] => Error Fetching http headers (...)"
It turned out to be an incompatibility between the SOAP server and the client requesting the SOAP service.
The header sent by the client script was malformed. The SOAP server expected the header to end with "\r\n", but the client was sending headers ending with "\n". The server would sit there for about 60 seconds after a request, and then throw the error message.
I had to check the source code of the soap server which did the strcmp on the headerbuf, against the actual contents of the HTTP header sent by the client.
I think the SOAP server was checking something like :
Code:
if (strcmp(headerbuf, "\r\n") == 0) {
.....
}
And just to get things going on the production box, I patched it to something like :
Code:
if (strcmp(headerbuf, "\r\n") == 0 || strcmp(headerbuf, "\n") == 0) {
.....
}
An upgrade of both server and client later solved it permanently.
EDIT: You are looking for this file in the PHP source code php{your-PHP-version-number-and-datetimestamp}/ext/soap/php_http.c
Recent comments
10 hours 44 min ago
11 hours 44 min ago
15 hours 31 min ago
16 hours 45 min ago
20 hours 21 min ago
1 day 3 hours ago
1 day 12 hours ago
1 day 14 hours ago
2 days 5 hours ago
2 days 7 hours ago