--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/e525dfa3-864b-4cda-824b-65207d25d264%40chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAF8qwaDecHiSTR-3UK9ARWuVTAFZzQDbbr2P0YM9bXs3SdMMLA%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAKXHy%3DfePJXeadH%2B0qdVyVrsHXnpJaZ21NOpsV81GMccjY%3DYgw%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw9tyx%2ByeG3zpGz-HVR%3DaEW4iBQwD2Ty1MozbQDEGLQ1UQ%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAKXHy%3DfePJXeadH%2B0qdVyVrsHXnpJaZ21NOpsV81GMccjY%3DYgw%40mail.gmail.com.
Won't this affect the way relative URLs in the fetched resource are rendered? For example, if I fetch "test.html" and it contains a href="../resource.html" in that, that'll have very different results if I'm rendering it by downloading the file and then opening it versus it being opened in the context of the right origin, right? I don't know that I'd expect the average user to appreciate the implications of that, I'd expect them to just be annoyed and click through (and then wonder why things aren't working).
Apart from that (and probably less important), this feels like just a generally unfriendly user experience, in the sense that I don't think anonymous FTP is less secure than HTTP (perhaps I'm forgetting something and am wrong here?) and, given that, it's hard for me to say that we should treat FTP differently from HTTP. It seems like that's exposing an implementation detail to the user in a particularly poor way. Given that we still have to support the network protocol, and we don't simplify any rendering code, this doesn't seem like a great win to me. Perhaps I'm not wise to the potential range of exploits we'd be excluding?
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAEoffTBFt-8mX00u%2BgQS8pyhnZ0UtgNAxAvhe7iqJ5XgaQ-8Gg%40mail.gmail.com.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/5a5416e1-ace5-4c20-b5d7-fe0bbcc9e11d%40chromium.org.
I am also surprised by the number of users encountering ftp links, though the number of actual page loads is much lower.Looking at the counter it seems like it includes navigations also to non-existing resources (strange "404" page) and to non-html resources. If speculating, it could even be that some/many loads were intended to be a download. For instance, trying to download html files (and images) from some web hotels would end up as navigations.A question: It sounds like you plan to change navigations to non-html resources like ftp://ftp.sunet.se/about/graph.png - will that also affect pages (if any) that use images hosted at ftp sites?
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/9cfe3d47-5dc5-4313-b35d-c3df3054095d%40chromium.org.
Tell me, who decided this? Disabling FTP is your personal decision?Let's ban https? In some particular cases, it is also not safe.
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/99a618da-5564-4f16-8e8e-6a3c91592693%40chromium.org.