[
https://issues.apache.org/jira/browse/NET-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13907398#comment-13907398
]
Sebb commented on NET-516:
--------------------------
Not quite sure what you mean by "byte trace".
I don't suppose there is a public FTP server which contains suitable example
files?
Alternatively, the output from running an FTP LIST command and/or MLST?
There is an example file in the NET source which can do both; you can run it
from the jar provided that commons-net.jar is in the same directory:
{code}
java -jar commons-net-examples-3.3.jar FTPClientExample
{code}
> 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, 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)
