Nathan Cox added the comment:
I have this issue intermittently with a server that I connect to, but the issue
(at least for me) seems to be the minBytesPerSecond configuration triggering a
remote disconnect of the connection.
--
nosy: +Nathan Cox
Changes by required field requiredfield...@gmail.com:
--
nosy: +required field
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16318
___
___
Lukasz Szybalski added the comment:
Hello,
We are having issues usign ftplib for implicit TLS over port 990
I'm referencing a solution that states
For the implicit FTP TLS/SSL(defualt port 990), our client program must build
a TLS/SSL connection right after the socket is created. But
Giampaolo Rodola' added the comment:
Have you tried to see what happens in passive mode (use: ftps.set_pasv(True))?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16318
___
Jeremy Brock added the comment:
Hello Giampaolo,
It is the same timeout in PASV with Prot_P, please see attached documentation.
Something I did not mention before is that the file being written shows up on
the server but I can't view it because it is being used by another process.
When the
New submission from Jeremy Brock:
Recently I have been working on a project to utilize the new FTP_TLS library
from ftplib in Python 2.7.3. What I found is that no matter what I try, when
prot_p() is called prior to transferring files to 2008 Server R2 running
FTP7.5, the python client
Changes by Ned Deily n...@acm.org:
--
nosy: +giampaolo.rodola
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16318
___
___
Python-bugs-list mailing
