This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author nagle
Recipients nagle, neologix
Date 2013-09-14.17:15:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1379178919.09.0.701878177992.issue18907@psf.upfronthosting.co.za>
In-reply-to
Content
The server operator at the US Securities and Exchange Commission writes to me: "There was a DNS issue that affected the availability of FTP at night. We believe it is resolved. Please let us know if you encounter any further problems.  Thanks, SEC Webmaster".

So this may have been a DNS related issue, perhaps a load balancer referring the connection to a dead machine.  Yet, for some reason, the Windows command line FTP client can recover from this problem after 20 seconds? What are they doing right? Completely retrying the open?
History
Date User Action Args
2013-09-14 17:15:19naglesetrecipients: + nagle, neologix
2013-09-14 17:15:19naglesetmessageid: <1379178919.09.0.701878177992.issue18907@psf.upfronthosting.co.za>
2013-09-14 17:15:19naglelinkissue18907 messages
2013-09-14 17:15:18naglecreate