commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (NET-516) parser problem occurs if the filename contains one or more characters of which the second byte of Shift-JIS code is 0x85
Date Mon, 24 Feb 2014 13:00:21 GMT

    [ https://issues.apache.org/jira/browse/NET-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13910264#comment-13910264
] 

Sebb commented on NET-516:
--------------------------

Thanks, I think I may be able to turn that into an input stream.

What happens if you change the control encoding to something more suited to the file names?
Does FTPClient still fail to parse the entries?
I'm wondering whether this is at least partly an encoding issue.

> parser problem occurs if the filename contains one or more characters of which the second
byte of Shift-JIS code is 0x85
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: NET-516
>                 URL: https://issues.apache.org/jira/browse/NET-516
>             Project: Commons Net
>          Issue Type: Bug
>          Components: FTP
>    Affects Versions: 2.0
>         Environment: windows
>            Reporter: Asha K S
>             Fix For: 2.0
>
>         Attachments: FTPSample.java, FTPTestSample.java, IIS FTP Files.zip, listfilesStreamBytes.txt,
notworking.png, working.png
>
>
> Problem occurs if the filename contains one or more characters of which the second byte
of Shift-JIS code is 0x85, on a windows Japanese machine when listing file names from IIS
FTP server.
> This was working fine in commons-net-1.4.0.jar . 
> [This relates to the NTFTPEntryParser]



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message