cancel
Showing results for 
Search instead for 
Did you mean: 

Alfresco download UTF-8 using FTP

framtk
Champ on-the-rise
Champ on-the-rise

Hi,

I have installed alfresco 5.1 with the installer on a windows machine running server 2012 r2.

I use FTP (filezilla) to upload and download folders that exceed the 2GB limit imposed on the zip compression but the transfer fails for files that contain UTF-8 characters.

The strange thing is that if i have a file or a single folder with non ascii characters (EG èàìßä) then i am able to upload and download it without problems but if the UTF-8 characters are in the name of a folder or file, let's say, 5-6 levels deep in the directory tree then the transfer will fail with a "path not valid" error.

I was wondering if this is an alfresco or an FTP error since, as i said, it works fine with single files or folders.

P.S. on the alfresco web interface i can see the non-ascii characters normally

3 REPLIES 3

mrks_js1
Star Contributor
Star Contributor

you mean the encoding of the files that fail is UTF-8 and you can reproduce the error?

does the path to the file contain spaces? try to give more detail on what works, and what does not work.

framtk
Champ on-the-rise
Champ on-the-rise

Some of the paths that work are with spaces so i don't think that's the problem. In the alfresco repository i have a folder named °üäöèéä? with inside it a file named °üäöèéä?.pdf 

Using FTP i can upload and download that folder without any problems. Now i in the repository i also have a folder structure with let's say 10 folders named A,B,C,D and so on, folder A contains folder B that contains folder C and  so on.

At the end of the tree i have a folder named something like "1° floor" with a file named  "1° floor scheme.pdf" inside, when i try to download the folder A with FTP i get the "path not valid" message. Removing the ° from the folder fixes the problem and i can download the folder A

mrks_js1
Star Contributor
Star Contributor

it might be, that the path of the document will stay "1° floor" even if you have successfully renamed the node via share/webdav. you can see the "real" path when checking the node via node browser. try to boil down if the issue is really not about the spaces, i think i have seen some similar issue lately. also try to search the here for ftp related topics.