When getting read timeout on persistent connect, socket is still alive and well and able to receive data.
This leads to getting trash from such connect on next request, or even receiving fully valid response, just not for the latest request, but for previous one.
This 06845559 kinda helps, but for complete safety it's might be better to reconnect on every uncertainty with connection - #112
Another workaround would be to mark timeout'd connects with a "dirty" flag and read out its buffer completely later, before next request or on php request shutdown.
When getting read timeout on persistent connect, socket is still alive and well and able to receive data.
This leads to getting trash from such connect on next request, or even receiving fully valid response, just not for the latest request, but for previous one.
This 06845559 kinda helps, but for complete safety it's might be better to reconnect on every uncertainty with connection - #112
Another workaround would be to mark timeout'd connects with a "dirty" flag and read out its buffer completely later, before next request or on php request shutdown.