Issue 1037516: ftplib PASV error bug (original) (raw)

Created on 2004-09-30 05:35 by wayland, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (5)
msg22574 - (view)	Author: Tim Nelson (wayland)	Date: 2004-09-30 05:35
Hi. If ftplib gets an error while doing the PASV section of the ntransfercmd it dies. I've altered it so that ntransfercmd does an autodetect, if an autodetect hasn't been done yet. If there are any problems (as I'm not a python programmer :) ), please either fix them or let me know.
msg22575 - (view)	Author: Andrew Bennetts (spiv)	Date: 2004-10-06 10:49
Logged In: YES user_id=50945 Did you mean to submit a patch with this bug report? It sounds like you did, but there's no files attached to this bug.
msg22576 - (view)	Author: Tim Nelson (wayland)	Date: 2007-01-16 00:02
Oops. I probably did, but I don't work in that job any more, so I'm afraid I don't have access to it. Sorry. You should, however, be able to correct it from the description.
msg62198 - (view)	Author: Giampaolo Rodola' (giampaolo.rodola) *	Date: 2008-02-08 14:53
> If ftplib gets an error while doing the PASV > section of the ntransfercmd it dies. Which kind of error? What do you mean by "dies"? If the server returns an error response while ftplib is attempting to open a passive data channel it is expected that an exception is raised.
msg103492 - (view)	Author: Giampaolo Rodola' (giampaolo.rodola) *	Date: 2010-04-18 14:21
Closing this out as invalid as an exception being raised after an invalid PASV response makes perfect sense.