Using accentuated directory names produces errors

Think you've found a bug? Post a description here.

Moderator: Serin

Post Reply
User avatar
mll
New User
Posts: 4
Joined: Sat Sep 23, 2006 8:04 am
Contact:

Using accentuated directory names produces errors

Post by mll » Sun Mar 25, 2007 8:10 am

Hi there,

While trying to upload a directory of photos whose name has accents "axéla" in my case), I got "550 Path does not exist" errors for each photo uploaded (but the photos do get uploaded yet). If I remove accents from the directory name, I get no error any more.
The client is Windows's integrated FTP client (explorer.exe ftp://myserver/mydir/).

Here are the logs of the session:

Code: Select all

Mar 25 13:54:39  0  CWD /IncomingFTP/FSE/
Mar 25 13:54:39 0 250 Change directory ok
Mar 25 13:54:39 0 MKD akéla
Mar 25 13:54:39 0 257 "/IncomingFTP/FSE/akéla"directory created
Mar 25 13:54:39 0 PWD
Mar 25 13:54:39 0 257 "/IncomingFTP/FSE" is the current directory
Mar 25 13:54:39 0 CWD akéla
Mar 25 13:54:39 0 250 Change directory ok
Mar 25 13:54:39 0 CWD /IncomingFTP/FSE
Mar 25 13:54:39 0 250 Change directory ok
Mar 25 13:54:39 0 NOOP
Mar 25 13:54:39 0 200 NOOP command received
Mar 25 13:54:39 0 CWD /IncomingFTP/FSE/
Mar 25 13:54:39 0 250 Change directory ok
Mar 25 13:54:39 0 PWD
Mar 25 13:54:39 0 257 "/IncomingFTP/FSE" is the current directory
Mar 25 13:54:39 0 CWD akéla
Mar 25 13:54:39 0 250 Change directory ok
Mar 25 13:54:39 1 Incoming connection request on interface xxx.xxx.xxx.xxx
Mar 25 13:54:39 1 Connection request accepted from xxx.xxx.xxx.xxx
Mar 25 13:54:39 1 USER USER
Mar 25 13:54:39 1 331 User USER, password please
Mar 25 13:54:39 1 PASS ***********
Mar 25 13:54:39 1 230 Password Ok, User logged in
Mar 25 13:54:39 1 OPTS utf8 on
Mar 25 13:54:39 1 501 Unsupported feature
Mar 25 13:54:39 1 PWD
Mar 25 13:54:39 1 257 "/" is the current directory
Mar 25 13:54:39 1 CWD /IncomingFTP/FSE/akla/
Mar 25 13:54:39 1 550 Path does not exist
I think the problem is around "OPTS utf8 on". Is there anything to do to fix this ?

Many thanks in advance,

MLL

User avatar
Serin
Site Administrator
Posts: 1785
Joined: Sat Jan 01, 2005 6:57 pm
Location: United States
Contact:

Post by Serin » Mon Mar 26, 2007 12:29 am

Looking at your log listing, it looks like the problem is you are spelling the directory differently when creating vs. changing to it. The log clearly shows you create the directory successfully with the accent in it, but try to change into a directory with a different name. The 550 error is exactly what you should expect.

You are creating a directory called "/IncomingFTP/FSE/akéla"

but trying to change to the directory "/IncomingFTP/FSE/akla/"

User avatar
mll
New User
Posts: 4
Joined: Sat Sep 23, 2006 8:04 am
Contact:

Post by mll » Mon Mar 26, 2007 2:00 am

Woudn't it be that Windows Explorer sends some UTF-8 coded sentence for "akéla" (because it sent "OPTS utf8 on") that, given CerberusFTP replied "501 Unsupported feature", could be misinterpreted server-side ?

I'm no character encoding wizard at all, but I've often seen accents dropped or defaced when different systems try to communicate.

User avatar
Serin
Site Administrator
Posts: 1785
Joined: Sat Jan 01, 2005 6:57 pm
Location: United States
Contact:

Post by Serin » Tue Mar 27, 2007 10:38 pm

I agree, it could be that WIndows Explorer is sending UTF-8 encoding, but that would be incorrect, since Cerberus FTP Server denies a request to initiate UTF-8 encoding.

I've been looking into supporting the UTF-8 optional encoding rules for internationalization, so I will look into this issue more in the next few weeks.

User avatar
mll
New User
Posts: 4
Joined: Sat Sep 23, 2006 8:04 am
Contact:

Post by mll » Wed Mar 28, 2007 2:05 am

Sure, Windows Explorer has a weird behaviour while jumping from non-UTF8 to UTF8 encoding, and not detecting it's unsupported server-side.

However, accepting UTF8 encoding is always a plus for an app, so kudos for planning support for it. :)

mll

Post Reply