Issue metadata
Sign in to add a comment
|
Vsftp issue with chrome(pc/mobile)
Reported by
jupiter...@gmail.com,
Dec 13 2016
|
||||||||||||||||||||||
Issue description
<b>Chrome Version : <Copy from: 'about:version'></b>
URLs (if applicable) :home ftp server
Other browsers tested:All other ftp client works. Worked on chrome before weeks ago
Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
Safari:
Firefox:
IE:
What steps will reproduce the problem?
(1)create ftp server with vsftpd on raspberry pi
(2)newiest version of chrome(worked weeks before)
(3)
What is the expected result?
Ftp server showing file list
https://m.imgur.com/wxx4p6A
What happens instead?
https://m.imgur.com/4SFi4GR
Urecognizable data received, report bug.
Please provide any additional information below. Attach a screenshot if
possible.
,
Dec 14 2016
,
Dec 28 2016
This is likely a duplicate of issue 676762 . You system locale is set to the same language as the FTP server is using (I'm assuming that's Korean?)
,
Dec 28 2016
,
Dec 30 2016
Raspberry pi is set on ENG, and my phones and computers are set to korean. I confirmed ftp working well on 'IE11', login error on MS edge, chrome shows as unrecognizable data. I can attach IE11 image if you need. - jupiter^bjy - 2016. 12. 29. 오전 3:35에 "mme… via monorail" < monorail+v2.3079273537@chromium.org>님이 작성:
,
Jan 3 2017
Thanks for the report. Assuming 192.168.0.13 is the right address of the ftp server, Could you upload the output of ftp://192.168.0.13?raw viewed on desktop Chrome? You can save it by right clicking on the output and choose 'Save as...'
,
Jan 4 2017
http://imgur.com/a/wJ6O6 As you see, using ?raw option display properly, only japanese gets broken, but lost functionality as FTP. For Edge, I didn't think it will work and - never seen it worked, for some reason. For IE, it works properly, but both korean and japanese are broken. And as you see, 192.168.0.13 is correct for FTP. I usually use external IP, but some bad guys can see it you know ;) 2017-01-03 12:24 GMT+09:00 jinsuk… via monorail < monorail+v2.1717598733@chromium.org>:
,
Jan 4 2017
It's very likely to be a duplicate of Issue 676762 as suspected in #c3. I can see in the screenshot some filenames with broken encoding, which could cause the ftp directory parser to fail in converting to UTF16 and return an empty string. I updated Issue 676762 with the analysis and a workaround. Will follow it up there.
,
Jan 4 2017
I couldn't search this via google as I post this bug, was it duplicate? A bit meaningless question: If broken encoding has something to do with, why 'IE11' works properly even if it's text is most broken? And I didn't saw major update on chrome for both PC and Android but why chrome doesn't work with ftp in both android and computer? 2017-01-04 20:36 GMT+09:00 jinsuk… via monorail < monorail+v2.1717598733@chromium.org>: |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ajha@chromium.org
, Dec 14 2016Labels: Needs-Milestone OS-Android