Opened 22 years ago
Last modified 19 years ago
#250 closed Bug report
Queue Processing does not respect retry settings
| Reported by: | anonymous | Owned by: | |
|---|---|---|---|
| Priority: | normal | Component: | Other |
| Keywords: | Cc: | ruisa, Tim Kosse | |
| Component version: | Operating system type: | ||
| Operating system version: |
Description
Using v2.1.3a:
Not using multiple connections.
Reproduce:
- Connect to site
- Find directory to download
- Right click - "Download As"
- Enter another username/password and hit ok
- Select Process Queue
Expected Results:
New connection attempt under entered username/password
should proceed, if the connection is not made, the
client should attempt to reconnect x number of times
after waiting for y seconds, as specified in the
settings dialogue.
Actual Results:
New connection attempt under entered username/password.
If connection is not made reconnection is attempted
IMMEDIATELY. Very frustrating for ftp servers with
auto-ban after x number of failed connections.
Change History (3)
comment:1 by , 22 years ago
comment:2 by , 21 years ago
This bug is still here in 2.1.7: can anyone please look at this
issue?
Not using multiple connections, whenever a transfer breaks,
the retry settings are not observed and retry is attempted
immediately, and if login is unsuccessfull (due to e.g.
maximum # of users having been reached) this usually
results in the user being banned for some time as successive
attempts are made without any delay between them.
comment:3 by , 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).
Logged In: NO
Hello. This happens on v2.1.5 manual transfer too.
Reproduce:
If the connection failed, FileZilla retries immediately, ignoring
the "time between retries" setting.