If an error is detected mid-stream, how about inserting some JS that will modify the DOM to insert a warning block at the top (or bottom) of the view port. You could include a link that when clicked would load the raw stream. Maybe we could achieve that by supporting a query parameter syntax, like: ftp://ftp.site.com/pub/?display=raw
That URL could be served as text/plain. -Darin On Mon, Jan 11, 2010 at 12:21 PM, Paweł Hajdan, Jr. <[email protected] > wrote: > Is there any security risks with passing raw ftp listings to the > renderer in case we can't parse them? We already have a check in the > code so that we will only make a data connection to the server we have > the control connection with. > > If it's ok to do so, I'd also like to include some message encouraging > the user to submit a bug report like "hey, Chrome FTP listing parser > is not compatible with this site". That would really help with > compatibility. The new listing parser is doing quite well, but I think > it's still not compatible enough to entirely replace the Mozilla code. > > -- > Chromium Developers mailing list: [email protected] > View archives, change email options, or unsubscribe: > http://groups.google.com/group/chromium-dev >
-- Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
