Drop support for subresources with legacy protocols. (removed)

We should block requests from HTTP/HTTPS documents that target "legacy" schemes (e.g. "ftp://my-awesome-ftp-server.com/yay.tiff"). That is, the `ftp://` image referenced in https://jsbin.com/petonig/edit?html,output would not load, as the document itself is not served from `ftp://`.

Specification

Public discussion

Status in Chromium

Removed (launch bug) in:

  • Chrome for desktop release 59
  • Chrome for Android release 59
  • Android WebView release 59

Consensus & Standardization

  • No public signals
  • No public signals
  • No public signals
  • No signals

Owner

Last updated on 2017-03-24