| Re: PHP-SOAP/5.4.21 SoapClient terminating POST without waiting for reply, but still complaining "error fetching http headers". [message #185826 is a reply to message #185821] |
Sun, 11 May 2014 12:22   |
Jerry Stuckle
Messages: 2598
Registered: September 2010
Karma:
|
Senior Member |
|
|
On 5/11/2014 7:20 AM, ghpille(at)gmail(dot)com wrote:
>
>>
>> There is a LOT between the client and the server scripts. PHP is only a
>>
>> small part of it.
>>
>>
>>
>> Salvatore is correct - PHP has nothing to do with the PHP packets
>>
>> itself. And I would be willing to bet the problem is NOT in your TCP/IP
>>
>> stack - such a problem wouldn't show up only on your machine with this
>>
>> particular SOAP request.
>>
>>
>>
>> My bet is you're assembling the SOAP requests incorrectly. Another
>>
>> option would be your SOAP client isn't decoding them properly.
>>
>>
>>
>> --
>
> The soap request is "assembled" by Symfony2, if I'm not mistaken.
>
> Suppose something is wrong with the soap-envelope. How could that make TCP misbehave?
>
> I ran tcpdump on the soap-client-machine. It is on that machine that the fin flag in the third packet was set.
>
> I'll concentrate on the TCP stack. Where do I start? vmxnet3?
>
Start by debugging your problem and determining the failing component.
PHP has NOTHING to do with the format of a TCP/IP packet.
Once you've determined the failing component, ask in a forum or
newsgroup appropriate to the failure.
If you are unable to do that, I would suggest hiring a consultant to
assist you (and no, I am not available).
--
==================
Remove the "x" from my email address
Jerry Stuckle
jstucklex(at)attglobal(dot)net
==================
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]