Most hostnames that aren't valid IPv4 addresses, but end in numbers are treated as valid, and looked up via DNS (for example, ). # Support for URLs with non-IPv4 hostnames ending in numbers Since Chrome 88, it was only available through a deprecation trial and is now disabled. In Chrome 87 it was turned off for fifty percent of users but could also be enabled through the command line. In Chrome 86 FTP support was turned off for pre-release channels (Canary and Beta) and experimentally turned off for one percent of stable users, though it could be reenabled via the command line. Proxy support for FTP was removed entirely in Google Chrome 76. A bug in Google Chrome 74 and later resulted in dropping support for accessing FTP URLs over HTTP proxies. Currently navigating to FTP URLs results in showing a directory listing or a download depending on the type of resource.

Google Chrome 72 and later removed support for fetching document subresources over FTP and rendering of top level FTP resources. In addition, more capable FTP clients are available on all affected platforms. Use of FTP in the browser is sufficiently low that it is no longer viable to invest in improving the existing FTP client. # FTP support removedĬhrome is removing support for FTP URLs. Visit for lists of current deprecations and previous removals.Ĭhrome 95 beta was released on Septemand is expected to become the stable version in late October, 2021.

Chrome u2f