Opened 21 years ago

Last modified 19 years ago

#518 closed Bug report

FZ cannot understand "451 Append/Restart not permitted"

Reported by: zhangweiwu Owned by:
Priority: high Component: Other
Keywords: Cc: zhangweiwu, Tim Kosse, gensec
Component version: Operating system type:
Operating system version:

Description

Hello. There are many wildly used ftp servers default to
not allow APPE command. Sometimes the upload
connection breaks, and FZ tries to APPE, receiving the
message:

451 format_de.tpl: Append/Restart not permitted.

FZ records an error, and tries it again. Failed certain
times, FZ state the file as "Too many error attempt."

What's worse, that if a user clears these file states, and
tries to upload them again, he goes into the error circle
again, each file fails certain times and quit from the
queue. The user actually get no way to upload the files
from the queue.

Yesterday I spent a night to upload about 9000 files,
about 300 files are not successfully uploaded. They are
nightmares to me. I can clear the status, but the queue
remain unsuccess because FZ always tries to tell the
server APPE without luck.

I suggest
1) filezilla recognize the "451 Append/Restart not
permitted." message and try to STORE in that case;
2) there be an option in the preference to let FZ never
use APPE.

Change History (3)

comment:1 by Tim Kosse, 21 years ago

One reason is that any reply code starting with a 4
represents an temporary error and indicates that the client
should try again.
Instead the server should send something like '550 APPE not
allowed'

comment:2 by gensec, 20 years ago

An option to disable append/restart should be the simplest to
implement.

I don't know whether the server is incorrect to return 451
instead of 550, but regardless, giving the user control solves
the problem.

comment:3 by Tim Kosse, 19 years ago

This bug report has been closed due to inactivity and has possibly
already been solved.

You can reopen this report if the issue still exists in the
latest version of FileZilla (Server).

Note: See TracTickets for help on using tickets.