This problem also happen on my smart phone.
My smart phone:
Chrome 54.0.2840.85
Android 6.0.1; F8332 Build/39.0.A.1.250
Xperia XZ

Unable to access the link provided in original comment, It displays error saying "This site can't be reached".
 
bhyfor@ Could you please provide a different link or minimal test case of this issue for further triaging.

Thanks!

I think Google IP is blackholed by China GFW.
Please just use a ProXY XD
I don't have Windows IIS FTP Server out of China.
This site have passed test on https://ftptest.net/

I make a port forward on my VPS.
Please try this: ftp://133.130.114.200
Thanks!

nope that address seems doesn't work.
I'll fix it soon

Not sure there's anything we can do here.  There's no way to tell what character encoding the FTP server is using.  Doesn't look to be UTF8, and figuring out an arbitrary character encoding definitely doesn't seem worth the effort (And is error prone).

Notepad++ says it's ANSI encode, and Notepad++ display the list normally.
FTP server is Windows IIS Ver 10.0.14393.0

I don't think we want to assume we're getting Windows-1252 directory listings, anymore than we want to assume UTF-8.

What is the filename that you expect? What is your local encoding?

The FTP response doesn't describe the encoding, so we use base::DetectEncoding(), which wasn't able to figure it out.

Looking at the bytes:

d2 bb 92 6b b1 cb c5 ae 20 bc d3 cc d9 90 7b 20 a6 c2 b0 e6 5f 62 65 74 61 5f 31 2e 30 2e 30 2e 61 70 6b

Not sure what encoding that is either. I tried Windows-1252 but that doesn't give any β...

file name: 一択彼女 加藤恵 β版_beta_1.0.0.apk
in my Notepad++: (file)

Deleted: screenshot.png 28.6 KB

	screenshot.png 28.6 KB View Download

Since that's Japanese, I guess it's most likely either EUC-JP or Shift-JIS.  Regardless, we don't have any deterministic way to detect that.

Thank you for providing more feedback. Adding requester "brajkumar@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

As per comment #12 removing myself from owners list.

In content/child/ftp_directory_listing_response_delegate.cc, ConvertPathToUTF16() says:

// Per RFC 2640, FTP servers should use UTF-8 or its proper subset ASCII,
// but many old FTP servers use legacy encodings. Try UTF-8 first.

The RFC is from 1999. Why are there even modern FTP servers not following the RFC?

Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot