> From: Justin Piszcz <[EMAIL PROTECTED]>
> I have tried with over 100s of ftp servers around the world.
On Tue, Apr 09, 2002 at 02:55:25PM +0200, Hrvoje Niksic wrote:
> It seems so. But I really find it strange that there would be an FTP
> server that fails in this scenario. I've only heard o
On Sun, Apr 07, 2002 at 05:05:10PM -0400, Glenn Maynard wrote:
> Oops. I fixed this in my tree, but since it's among a bunch of
> OutputJob changes I forgot to send it in. Sorry about that.
>
> FileSetOutput.cc: fix output width instead of aborting.
Thanks. I have applied the patch, and to 2.4
Netgain specifics are closed source and proprietrary, however the BST protocol is
open.
Bug in BST/TCP/NetGain, no matter which it is, the rollback option [when used]
appears to fix the problem quite nicely.
"Alexander V. Lukyanov" wrote:
> On Tue, Apr 09, 2002 at 02:55:25PM +0200, Hrvoje Niksic
Justin Piszcz <[EMAIL PROTECTED]> writes:
> --12:12:21-- ftp://war:*password*@0.0.0.0:21//iso/file.iso
>=> `iso/file.iso'
> ==> CWD not required.
> ==> PASV ... done.==> RETR file.iso ... done.
> Length: 737,402,880
>
> 24% [>] 180,231,952 37
On Tue, Apr 09, 2002 at 02:55:25PM +0200, Hrvoje Niksic wrote:
> It seems so. But I really find it strange that there would be an FTP
> server that fails in this scenario. I've only heard of such proxy
> failures, and that's not applicable to your case.
I think it is tcp layer bug. Does the Net
