automatic ftp and the extension list

[Arakrys]

hi,
this question can probably only be answered by Christian Ghisler.

I just found out that uploading a gif as ascii file causes our ISP's FTP server to make file handling through FTP in that particular subdirectory impossible. It just breaks the connection when trying to up/download or delete, even when it is not the gif file.

I did not intend to upload the file in ASCII, I had chosen 'automatic'. And I did not add *.gif to the ASCII list. But I did notice that I made a mistake while adding an extension: I inserted a _comma_ (,) before the last extension. The others extensions are divided by spaces.

Now I wonder, is it possible that this comma in my extension list caused the gif to be uploaded in ASCII anyway, maybe by breaking the way TC handles this list?

If so, would it be an idea to add a filter when modifying the list, to prevent such hard-to-find mistakes?

Arakrys

[ghisler(Author)]

Did you upload in automatic mode? Then it depends on what wildcard you have set. Example: If you have set *. as text files, then a file named sample,gif will be a file with no extension matched by the above wildcard, and will therefore be uploaded as text.