|
php.net | support | documentation | report a bug | advanced search | search howto | statistics | random bug | login |
PatchesPull Requests |
|||||||||||||||||||||||||||||||||||||
Copyright © 2001-2025 The PHP GroupAll rights reserved. |
Last updated: Sun Oct 26 06:00:02 2025 UTC |
Description: ------------ When I try to make a SOAP call to a server that doesn't reply with an answer, my client keeps on waiting until the server finished it's work. Shouldn't one-way operation be "fire-and-forget" in order to make more sense? This could be solved by returning a HTTP 200 response and closing the socket, right after the SOAP call was received by the server. Reproduce code: --------------- Server code: ------------ public function onewaytest() { sleep(50); } Client code: ------------ $soap = new SoapClient(null, '...'); $starttime=time(); $soap->onewaytest(); echo time()-$starttime." sec\n"; Expected result: ---------------- Just the network time-overhead caused by HTTP connect and POST. Actual result: -------------- Above 50 sec.