Home Forums .NET libraries Xceed SFTP/FTP for .NET Xceed Ftp is unable to pick/read the files, which have space character at end or start of file name.

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • User (Old forums)
    Member
    Post count: 23064
    #21209 |

    We have ftp at unix server.

    Xceed Ftp is unable to pick the files which have space character at end or start of file name.

    Althouth Xceed Ftp can detect those file, but it trims the space at the start or end of file name, that why it failed to pick those files from unix ftp.


    Its very importatnt for our product to work, so please let me know as soon as Xceed fixes this defect.

    —Thanks.

    Applies to Xceed FTP for .NET. Imported from legacy forums. Posted by Ransa (had 3497 views)

    User (Old forums)
    Member
    Post count: 23064

    Information obtained from http://blogs.msdn.com/brian_dewey/archive/2004/01/19/60263.aspx :

    Due to the layering of Windows architecture, the definition of a “legal” file name may vary depending upon the component of the operating system you are dealing with.

     

    ·          NTFS and the Posix subsystem have the most permissive definition of a “legal” name. The name may be up to 32,768 Unicode characters long. The name can contain trailing periods, trailing spaces, and two files may have names that differ only in case (e.g., README.TXT and readme.txt).

    ·          The Win32 subsystem enforces additional constraints on legal file names. The name can be at most MAX_PATH characters long (defined in windef.h as 260 characters), may not have trailing dots or spaces, and file names are case preserving, not case sensitive — if two files exists with names that differ only in case, you will only be able to manipulate one of them through Win32 APIs.

     

     

    Therefore, the problem you are facing with trailing spaces is not due to a defect in our component.  Actually, it is an operating system (Win32 subsystem) limitation.  

     

    Also, a filename with a leading space will be reported without this space when the FTP server responds to a ls command. This makes the file impossible to be downloaded. 

     

     

    Applies to Xceed FTP for .NET. Imported from legacy forums. Posted by Ghislain (had 1608 views)

    User (Old forums)
    Member
    Post count: 23064

    The point is xceed ftp component is not able to pick the files, which have spaces at start and end of file.

    There are some ftp-server for unix system, which supports these files, and our client/users uses them and we need to support it.

     

    when i do ftp comment to get the file list and download the file (don’t trim the spaces), its working.

    so what xceed can help is, instead of trimming the file-names comes from FTP server, use as it is, solves this.

     

    It will be great help for us, if we can get handle  of such file too, as we are dealing with such users.

    Its will also extents xceed ftp functional area and very helpful for users like us. 

     

    Thanks for your quick responce.

     

    Applies to Xceed FTP for .NET. Imported from legacy forums. Posted by Ransa (had 1437 views)

    User (Old forums)
    Member
    Post count: 23064

    Unfortunately, from the financial point of view, it would cost us too much to alter the way we are trimming the leading and trailing spaces from the filenames when we consider the possible benefits.  Unless you are willing to pay for this kind of development, it is probably easier to convince your customer to stop using trailing and leading spaces in their filenames (if this is possible). 

    If you are very serious about this feature, contact sales@xceed.com (it’s considered custom development) but I think you won’t like the price tag.

    Applies to Xceed FTP for .NET. Imported from legacy forums. Posted by Ghislain (had 2338 views)

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.