Google Chrome 82 won't support FTP anymore - gHacks Tech News

ADVERTISEMENT

Google Chrome 82 won't support FTP anymore

Google Chrome 82 won't support FTP anymore according to the recently published "Intent to Deprecate: FTP Support" document by Google.

All modern web browsers support FTP at the time of writing. Users may click on ftp:// links or type them manually in the browser's address bar to open a connection to the site.

Google argues that the implementation of FTP in Chrome does not support encrypted connections and that usage is too low, the company said that 0.1% of users use FTP, to justify spending resources on integrating secure FTP functionality in the browser.

google chrome ftp support end

The company opened a bug on the official Chromium bug tracker in 2015 to remove built-in support for FTP from Chrome and this bug has been revived recently to remove FTP components from Chrome.

A bug was filed by Mozilla on Bugzilla, Firefox's bug tracking site that referred to Google's bug; Mozilla decided against the removal at the time and the last entry dates back two years.

Mozilla did implement an option in Firefox 60 in 2018 however to disable FTP support in the browser.

Chrome 72 started to block support for fetching resources from FTP and rendering top level FTP resources, Firefox 61 introduced the blocking of resources from FTP as well, and Chrome 76 dropped proxy support for FTP.

Google made the decision to remove the two remaining FTP capabilities from Google Chrome, namely displaying a FTP directory listing and downloading resources from FTP directly.

We would like to deprecate and remove this remaining functionality rather than maintain an insecure FTP implementation.

The timeline for FTP deprecation in Chrome:

  • Chrome 78: Start of FTP deprecation. Finch controlled flag and enterprise policy for controlling overall FTP support
  • Chrome 80 (Q1 2020): gradual turndown of FTP in stable.
  • Chrome 82: FTP related code and resources are removed.

When Chrome 82 or newer encounter FTP resources, Chrome attempts to redirect the request to the default FTP handler on the system. Google has not revealed how it plans to handle configurations in which Chrome is the default FTP handler.

Chrome users who use to load PAC scripts from FTP need to "migrate to other means for fetching PAC scripts" according to Google once Chrome 82 is released to the stable channel. Under 0.0002% of users fetch PAC scripts over FTP according to Google.

Are companies that develop browsers based on Chromium affected by the decision as well? Yes they are as Vivaldi, Microsoft, Opera or Brave all use Chromium as the base. Companies who want to continue supporting FTP would have to change the code to make sure support remains available in the browser.

It seems likely that most browsers won't support FTP anymore at the end of 2020. FTP is not going away just yet though; FTP clients, e.g. FileZilla or FTP Rush are available and may be used to access these resources.

Now You: What is your take on the FTP deprecation in Chrome? (via Techdows)

Summary
Google Chrome 82 won't support FTP anymore
Article Name
Google Chrome 82 won't support FTP anymore
Description
Google Chrome 82 won't support FTP anymore according to the recently published "Intent to Deprecate: FTP Support" document by Google.
Author
Publisher
Ghacks Technology News
Logo
Advertisement

Previous Post: «
Next Post: »

Comments

  1. Arne Anka said on August 16, 2019 at 11:55 am
    Reply

    “usage is too low, the company said that 0.1% of users use FTP”

    Tracking their users they are – what a surprise it is…

    1. Martin Brinkmann said on August 16, 2019 at 12:57 pm
      Reply

      Besides, 0.1% of Chrome’s user base is not really that low. We don’t know the exact numbers, but if it is 500 million users, 500.000 users would use FTP.

      1. DJ said on August 19, 2019 at 11:29 am
        Reply

        500,000k?

      2. Martin Brinkmann said on August 19, 2019 at 11:39 am
        Reply

        500,000, sorry for the mixup.

    2. Paul Cameron said on October 18, 2019 at 1:08 am
      Reply

      I’m developing a photography website that functionally depends on the full implementation of FTP. Users can with a single click of a button, download all their photos and videos directly from an FTP server housed in the photographer’s studio. If Google removes the FTP client from Chrome, it will kill my business. How do I stop this from happening?

  2. Ascrod said on August 16, 2019 at 1:11 pm
    Reply

    Since Chrome is deprecating FTP, I guess that means the rest of the internet will deprecate it as well. Firefox certainly tried a few years back, and I’m sure it won’t be the last time.

  3. Ben said on August 16, 2019 at 1:48 pm
    Reply

    > the company said that 0.1% of users use FTP, to justify spending resources on integrating secure FTP functionality in the browser.

    So just leave normal FTP in there?

  4. Anonymous said on August 16, 2019 at 3:20 pm
    Reply

    Chosen excerpts from the bugzilla:

    “Absolutely ridiculous. Just because Chrome does something does not mean Firefox needs to follow!”

    “As for the actual FTP support: The code has been stable for a very long time and doesn’t really require any maintenance.”

    “Please find out the true reason for Google to drop this from Chrome before considering doing the same.”

    Mozilla will probably do it too some day if Google does it. The FireFTP classic extension may have been a replacement but it does no longer exist and I don’t know if webextensions can even do that. WinSCP is another FTP client.

  5. Paulus said on August 16, 2019 at 3:58 pm
    Reply

    I have never used that option in any brand of browser. Why use that option when i am already 18 years a happy user of the FileZilla 64 Bit (latest version. 3.43.0) program, witch provides better security and more options?

  6. NobodyShouldCare said on August 16, 2019 at 4:26 pm
    Reply

    FTP is something the average user hardly needs and FileZilla is a better choice anyway. Additionally, many public FTP servers offer a Web interface via HTTP (i.e. https[://]ftp[.]mozilla[.]org/pub/firefox/releases/) so nothing will really change.

  7. chesscanoe said on August 16, 2019 at 5:04 pm
    Reply

    I rarely use FTP, but when I do, I use FileZilla with success, just out of a long time habit.

  8. md said on August 16, 2019 at 5:54 pm
    Reply

    When will Google deprecate DNS?

    “It’s insecure anyway, here’s a whitelist of “AI approved” websites you’re allowed to visit”

  9. Popcorn said on August 16, 2019 at 7:12 pm
    Reply

    Some of you guys, geez! Why load up filezilla if you just wanna pull some files off a ftp server? I’ve never used chrome so this has no effect on me.

  10. Anonee said on August 16, 2019 at 7:15 pm
    Reply

    Good news! The more bloat Google strips from the browser, the better!

    If you need ftp support that badly, go grab your old AOL cd and set up your dial-up connection so that you can then use your usenet client to download the latest release of WinSCP and use that for ftp instead.
    For the rest of us, we’ll stick to http(s) over fiber optic for up/downloading our files. :)

  11. Yuliya said on August 16, 2019 at 10:51 pm
    Reply

    What? I honestly thought FTP support was already out of current Chromium o.O It has been a while since last time that I used this protocol.

  12. Gerold Manders said on August 17, 2019 at 1:04 am
    Reply

    On irregular (but often) intervals I need to pull data from one continent to another. Often enough that automatizing these steps was preferred. The person on the other end insisted that it needed to be done win Windows batch. Ugh.

    During that whole process, (S)FTP(S) was tried first. After all, Windows command line has FTP build-in. Tried several FTP servers on my end in combination with Windows FTP clients on the other end. Always slow. WinSCP? Slow.

    Then I discovered WebDAV, which was pretty easy to setup on my end and using the (command-line) client CarotDAV on the other end. With FTP transfers would take an hour on average. With WebDAV transfers are done on average between 8 to 10 minutes.

    Since then (S)FTP(S) has been dead to me. The last time I used FTP in any way or form to transfer files is easily more than 5 years ago. So I won’t miss it.

    However, that is my n = 1 experience, which is certainly not similar to others who might love ftp still. Google is starting to dictate what we can or cannot do on the internet. Of course, they do this already for years, but lately they don’t care doing this in the shadows anymore. Which is worry-some.

    Anyway, FireFox is my main browser and Opera is the only chromium-based browser I allow on my systems.

    1. mokeefoogowalla said on August 17, 2019 at 5:02 am
      Reply

      @Gerold Manders

      Are you saying you have found that WebDAV is faster than FTP, or did you mean FTPS, or both?

      I’ve never used WebDAV, but I know FTP is faster than FTPS.

      Also, I see WebDAV can use either HTTP or HTTPS, were I imagine with HTTPS it’s likewise comparatively slower in that regard, right?

      In other words, call me daft, but I don’t understand what you’re actually comparing here, but I am earnestly curious to know.

      Regardless, thanks for this tip about WebDAV. As need be, I will check it out more, but if there’s lacking point-and-click free-software support, then it’s likely not a fit for my cretinous requirements.

  13. mokeefoogowalla said on August 17, 2019 at 4:26 am
    Reply

    Back in the day, for those in the know, Firefox+DownThemAll!+Filemare was a great way to find and download tons of “free” media via FTP. But alas, those days are sadly gone.

    Nevertheless, FTP is still a simple way for even non-geeks to serve/share files, such as with FileZilla and private FTP servers.

    As for Chrome dropping FTP support, I understand the privacy concerns with using FTP connections, but there is FTPS and such.. As for the security concerns, I don’t understand how FTP is that complicated in that regard, as it’s rather basic/static with no need for JS and such. Yet I imagine there’s some complicated security concerns with MITM attacks, server-side scripts and/or such, but IDK.. Regardless, the clear issue is this:

    “Google argues that the implementation of FTP in Chrome does not support encrypted connections and that usage is too low, the company said that 0.1% of users use FTP, to justify spending resources on integrating secure FTP functionality in the browser.”

    So that’s that.

    That said, I wish Firefox would integrate DownThemAll! functionality with continued FTP support and more.

  14. Anonymous said on August 17, 2019 at 11:15 pm
    Reply

    Why stop there. Chrome should drop HTTP and HTTPS support aswell.

  15. Dzomba said on August 18, 2019 at 12:27 am
    Reply

    I’m using RaiDrive (just google it, I don’t know if I should post link) and it’s really simplify things for me.
    You guys should check it out and try it for your self. After installation you just need to add your drive of choice, from Google Drive, Microsoft OneDrive, Dropbox etc. to NAS (WebDAV, SFTP, FTP).

  16. JohnIL said on August 18, 2019 at 2:53 am
    Reply

    The biggest issues with Google is their manipulation of what is supported and not supported. Who made Google the entity that decides anything, and why do other browsers simply fall in line.

    1. Anonymous said on August 18, 2019 at 7:56 pm
      Reply

      Their marketshare. Like Microsoft did in IE glory days. It was Microsoft, now it’s Google, tomorrow who knows. Make no mistake, this will never change, it’s simple mathematics.

    2. boboobobobby said on August 20, 2019 at 10:35 am
      Reply

      Q: Who made Google the entity that decides anything?
      A: We vote for such with our money and time.
      Q: Why do other browsers simply fall in line?
      A: It’s economics.

      1. Anonymous said on August 21, 2019 at 11:24 pm
        Reply

        > We vote for such with our money and time.

        Do most of users make a conscious and informed decision for what browser to use, or just use the default one whatever it is ?

        > It’s economics.

        Which doesn’t explain anything nor implies any form of legitimacy.

  17. Jesus Pinte said on August 26, 2019 at 4:41 am
    Reply

    FTP is complex to set up. Binfer is a more secure alternative. See Binfer as FTP alternative

Leave a Reply

Check the box to consent to your data being stored in line with the guidelines set out in our privacy policy

Please note that your comment may not appear immediately after you post it.