Custom Query (8142 matches)
Results (346 - 348 of 8142)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #3663 | server:port isn't parsed correctly | |||
| 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. |
|||
| #400 | server:cant open shared files | |||
| Description |
when downloading files from server, it seems try to open the file in "rw" mode instead of "ro" mode |
|||
| #112 | server: don't change case of file | |||
| Description |
If the FTP server gets an all uppercase file, it changes it to lowercase. It should preserve the case, or at least make it a config option. |
|||
