[webkit-dev] Request for position: Allow Navigator.registerProtocolHandler to register FTP related schemes.
asanka at chromium.org
Mon May 17 12:19:05 PDT 2021
I sent out an 'intent to implement and ship' for adding FTP related schemes
to the list of safelisted schemes for use with registerProtocolHandler. I'd
like to solicit your opinion on this change.
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.
Search tagsftp <https://www.chromestatus.com/features#tags:ftp>,
TAG review statusNot applicable
Interoperability and Compatibility
Gecko: Worth prototyping (
filtering out credentials from outgoing FTP links.
WebKit: N/A Safari does not support `registerProtocolHandler`.
Web developers: Positive (
Same as other schemes in registerProtocolHandler. Since ftp was a protocol
that used to be supported by the browser, internal ftp links might exist
that assume in-browser support in assessing their security risks. A custom
protocol handler will necessarily expose ftp URLs to the handler.
Registering one may violate administrator assumptions about the URLs not
leaving their organization when users click on them.
Is this feature fully tested by web-platform-tests
Link to entry on the Chrome Platform Status
Links to previous Intent discussionsIntent to Ship:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev