It seems apropos to close a timed out connection and allow retry logic to attempt reconnection. That this situation has resulted in a 408 Request Timeout response status code [1] is provided to the requestor, after retries have failed, seems good

And the Magic 8 Ball says…Outlook good! 😊 

[1] 408 Request Timeout - https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/408


Have a good one; keep it, light.
Kindly,
rabbit
. .. … ‘…^,^


Sent from Callisto House :: decentralized mobile homeless solutions



> On Oct 7, 2022, at 17:01, tim Rowledge <tim at rowledge.org> wrote:
> 
> So far as I can see the WebClient code does not try to handle socket timeouts etc. If I handle NetworkError by faking a WebResponse with a 408 code, Am I The Asshole? Will it cause the entire intertoobs to catch fire?
> 
> tim
> --
> tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
> No one is listening until you make a mistake
> 
> 
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20221007/7a8fe5b5/attachment.html>