1.4.3 should now catch this exception and also in it's default configuration will no longer set a socket timeout unless one has been specifically set in the site.cfg file.
1.4.3 should now catch this exception and also in it's default configuration will no longer set a socket timeout unless one has been specifically set in the site.cfg file.