Opened 16 years ago
Last modified 16 years ago
#3663 closed Bug report
server:port isn't parsed correctly
| Reported by: | michael_de | Owned by: | |
|---|---|---|---|
| Priority: | normal | Component: | FileZilla Client |
| Keywords: | Cc: | michael_de, Tim Kosse | |
| Component version: | Operating system type: | ||
| Operating system version: |
Description
Version: 3.1.0.1
OS: Windows Vista Business SP1 (x64)
I used to enter example.com:1234 and it worked well in previous versions (3.0.x or something). However since I updated to 3.1.0.1, filezilla still writes the number behind the colon into the port field, but writes "[example.com:1234]" into the server field (instead of writing "example.com").
This results in a
Status: Resolving address of example.com:1234
Status: Connection attempt failed with "EAI_NONAME - Neither nodename nor servname provided, or not known".
Trace: CRealControlSocket::OnClose(11001)
Trace: CFtpControlSocket::ResetOperation(66)
Trace: CControlSocket::ResetOperation(66)
Error: Could not connect to server
Status: Waiting to retry...
error message.
Should be fixed in 3.1.1-rc1