Opened 13 years ago

Last modified 12 years ago

#2654 closed Feature request

Case insentitivity (option)

Reported by: palswim Owned by:
Priority: normal Component: FileZilla Client
Keywords: Cc: palswim, Tim Kosse
Component version: Operating system type:
Operating system version:

Description

I've found Filezilla doesn't like when the server switches case in its responses. Here are logs from me trying to transfer "TestDir" to my SFTP server:

Status: Connected
Status: Starting upload of C:\[...]\Test Dir\file_One.txt
Command: CD /parent/Test Dir/
Status: Starting upload of C:\[...]\Test Dir\File_two.txt
Command: CD /parent/Test Dir/
Response: Directory /parent/Test Dir: failure
Command: CD /parent/
Response: Directory /parent/Test Dir: failure
Command: CD /parent/
Response: Remote working directory is now /parent/
Command: MKD Test Dir
Response: Remote working directory is now /parent/
Command: MKD Test Dir
Response: Directory created successfully
Command: CD /parent/Test Dir/
Response: mkdir /parent/Test Dir: bad message
Command: CD /parent/Test Dir/
Response: Remote working directory is now /parent/test dir/
Error: Upload failed
Response: Remote working directory is now /parent/test dir/
Error: Upload failed

(The initial CD errors occur because the server has to create "Test Dir" and then the MKD error occurs since the previous MKD command already created "Test Dir" - no problems there.)

I believe the upload errors occur because the client issues the "CD /parent/Test Dir/" command, and the server responds with "/parent/test dir/". Since this is a Windows host, those two locations are the same and are valid. I don't suggest that Filezilla always ignore case, since UNIX hosts are case-sensitive, but maybe if Filezilla had a per-site option to ignore case, that could resolve this issue.

So feature: A per-site option to use case-insensitive comparisons when validating server responses (and other cases, where appropriate).

Change History (2)

comment:1 Changed 12 years ago by Tim Kosse

Please try the most recent FileZilla 3 beta.

comment:2 Changed 12 years ago by sf-robot

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).

Note: See TracTickets for help on using tickets.