Opened 17 years ago
Last modified 17 years ago
#3505 closed Bug report
Invalid Port Number
Reported by: | arnie1066 | Owned by: | |
---|---|---|---|
Priority: | normal | Component: | FileZilla Client |
Keywords: | Cc: | arnie1066, Tim Kosse | |
Component version: | Operating system type: | ||
Operating system version: |
Description
If you type a textual address into the host box in either the quick connect or the manager, the program fails with the message:
Could not parse server address:
Invalid port given. The port has to be a value from 1 to 65535
This same message occurs regardless of what port number is used.
There is no reason, that i am aware of, why the textual host value should not work (it works in all browsers and other ftp clients). If text is not supported, it should mention that and ignore the port number, (which was correct) until a numerical value for the host is entered.
Attachments (1)
Change History (4)
by , 17 years ago
Attachment: | ftp_filezilla.JPG added |
---|
comment:1 by , 17 years ago
User error. Protocol specifier ends with double slashes, not backslashes.
comment:2 by , 17 years ago
While i may have had a senior moment involving the double slashes, the message that appears is still incorrect, the port number was perfectly OK, the message should have indicated a problem with the address as type (which it did kind of) but not mention the port number at all as that totally threw me of the track, i may have spotted my rather stupid error if the message had not mentioned the port number.
Thanks for checking it out so quick though.
comment:3 by , 17 years ago
A colon after the host separates host from port.
If you enter "ftp:
somehost.exmple", the host is "ftp" and the port is "
somehost.example". So the error message is correct.
port error with version