Add "ftp", "ftps", and "sftp" to the list of protocols available for registration via registerProtocolHandler(). FTP is now deprecated and will imminently be removed from the codebase. Allowing websites to register themselves as handlers for ftp:// URLs makes it possible to build easy to use gateways for legacy ftp sites. In addition we propose adding related protocols "ftps" and "sftp" to the list. Google Chrome/Chromium was not handling these URL schemes.

Motivation

FTP is now no longer natively supported in Chromium derived browsers as well as Firefox. Safari never supported it in the first place. The dominant use-case for in-browser support was to download things via anonymous FTP. This usecase can be served by allowing `ftp` to be treated as a custom registrable protocol. Thus any website can advertise and handle FTP URLs and provide access to resources over FTP.

Specification

Specification link


Unknown standards status - check spec link for status

Status in Chromium

Blink>HTML>CustomHandlers


In development (tracking bug)

Consensus & Standardization

After a feature ships in Chrome, the values listed here are not guaranteed to be up to date.

Owner

Comments

https://html.spec.whatwg.org/multipage/system-state.html#safelisted-scheme is the location of the safelist that is proposed to be modified. Spec issue is https://github.com/whatwg/html/issues/6583

Search tags

ftp, registerprotocolhandler,

Last updated on 2021-08-29