Skip to content

Add FTP related protocols to the registerProtocolHandler safelist. - #6584

Merged
domenic merged 1 commit into
whatwg:mainfrom
asankah:main
Feb 14, 2022
Merged

domenic merged 1 commit into
whatwg:mainfrom
asankah:main

Conversation

@asankah

@asankah asankah commented Apr 14, 2021 •

Copy link
Copy Markdown
Contributor

Closes #6583

(See WHATWG Working Mode: Changes for more details.)


/system-state.html ( diff )


/acknowledgements.html ( diff )
/system-state.html ( diff )

@asankah

asankah commented May 21, 2021

Copy link
Copy Markdown
Contributor Author

Adding @domenic as well.

I updated the PR description to reflect that Firefox has reacted positively to the proposed change.

@annevk

annevk commented May 25, 2021 •

Copy link
Copy Markdown
Member

In the discussion with @valenting you mentioned removing credentials. Is that something you ended up pursuing? If so, it should probably be part of the standard, no? (Although I suppose we can only really do it for ftp, I'm not sure if that makes sense then.)

@annevk annevk added addition/proposal New features or enhancements topic: custom protocols labels May 25, 2021
@domenic

domenic commented May 26, 2021

Copy link
Copy Markdown
Member

Yes, per the change in https://chromium-review.googlesource.com/c/chromium/src/+/2826871 it looks like that is what was implemented. @asankah can you update this PR to specify that behavior?

@domenic

domenic commented Aug 17, 2021

Copy link
Copy Markdown
Member

@asankah ping on updating the PR to match what Chromium does.

@asankah

asankah commented Oct 9, 2021

Copy link
Copy Markdown
Contributor Author

@domenic @annevk I looked at adding it, but the spec already contains the following text:

Leaking credentials. User agents must never send username or password information in the URLs that are escaped and included sent to the handler sites.

This already captures what was agreed upon regarding how ftp/ftps/sftp should be handled.

@annevk

annevk commented Oct 11, 2021

Copy link
Copy Markdown
Member

@asankah the ask is to make that explicit in the processing model. And perhaps it should be exclusively in the processing model, as it's not clear if that note also applies to mailto:username@server.example for instance (it shouldn't, because that would make the feature useless).

@asankah

asankah commented Oct 11, 2021

Copy link
Copy Markdown
Contributor Author

@annevk Ohh. Gotcha. I'll update the patch to address that.

@annevk

annevk commented Jan 21, 2022

Copy link
Copy Markdown
Member

Hey @asankah, is this still on your radar? We've been thinking of shipping this behavior in Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=1705202.

cc @valenting

@hamishwillee

hamishwillee commented Feb 7, 2022 •

Copy link
Copy Markdown
Contributor

@asankah @annevk Any more news on this? I'm hoping to update the MDN documentation, but if https://bugzilla.mozilla.org/show_bug.cgi?id=1705202 goes in and this PR does not then I will need to update browser compatibility data in a more complicated way, as this will end up being non-spec behavior in a released platform

@asankah

asankah commented Feb 7, 2022

Copy link
Copy Markdown
Contributor Author

Whoops. Yeah, on it.

@domenic

domenic commented Feb 7, 2022

Copy link
Copy Markdown
Member

The rebase appears to have gone poorly, could you retry?

Comment thread source Outdated
Comment thread source Outdated
Comment thread source Outdated
@asankah
asankah force-pushed the main branch 2 times, most recently from 223c6bb to 18694ba Compare February 7, 2022 18:24
Comment thread source
allowing administrators to disable custom handlers on certain subdomains, content types, or
schemes.</p>

<p><strong>Leaking credentials.</strong> User agents must never send username or password

@asankah asankah Feb 7, 2022 •

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note that I removed the Leaking Credentials section since it is addressed in the processing steps.

The part about resources that may require credentials is, I believe, addressed in the "Leaking private data" section which warns about private URLs in general.

@domenic domenic left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Will give it a day in case @annevk wants to do an additional review.

asankah added a commit to asankah/web-platform-tests that referenced this pull request Feb 7, 2022
`registerProtocolHandler` allows registering `ftp`, `ftps`, and `sftp`
protocols as of whatwg/html#6584.

This change adds tests to ensure that `registerProtocolHandler` allows
registering those protocols and to ensure that embedded credentials are
removed prior to invoking the custom protocol handler.
asankah added a commit to asankah/web-platform-tests that referenced this pull request Feb 7, 2022
`registerProtocolHandler` allows registering `ftp`, `ftps`, and `sftp`
protocols as of whatwg/html#6584.

This change adds tests to ensure that `registerProtocolHandler` allows
registering those protocols and to ensure that embedded credentials are
removed prior to invoking the custom protocol handler.
asankah added a commit to asankah/web-platform-tests that referenced this pull request Feb 7, 2022
`registerProtocolHandler` allows registering `ftp`, `ftps`, and `sftp`
protocols as of whatwg/html#6584.

This change adds tests to ensure that `registerProtocolHandler` allows
registering those protocols and to ensure that embedded credentials are
removed prior to invoking the custom protocol handler.
asankah added a commit to asankah/web-platform-tests that referenced this pull request Feb 7, 2022
`registerProtocolHandler` allows registering `ftp`, `ftps`, and `sftp`
protocols as of whatwg/html#6584.

This change adds tests to ensure that `registerProtocolHandler` allows
registering those protocols and to ensure that embedded credentials are
removed prior to invoking the custom protocol handler.
asankah added a commit to asankah/web-platform-tests that referenced this pull request Feb 8, 2022
`registerProtocolHandler` allows registering `ftp`, `ftps`, and `sftp`
protocols as of whatwg/html#6584.

This change adds tests to ensure that `registerProtocolHandler` allows
registering those protocols and to ensure that embedded credentials are
removed prior to invoking the custom protocol handler.
asankah added a commit to asankah/web-platform-tests that referenced this pull request Feb 8, 2022
`registerProtocolHandler` allows registering `ftp`, `ftps`, and `sftp`
protocols as of whatwg/html#6584.

This change adds tests to ensure that `registerProtocolHandler` allows
registering those protocols and to ensure that embedded credentials are
removed prior to invoking the custom protocol handler.
@hamishwillee

Copy link
Copy Markdown
Contributor

@domenic No comment from @annevk - should this go in?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Development

Successfully merging this pull request may close these issues.

Add FTP related protocols to the registerProtocolHandler safelist.

4 participants