Deprecate loopback access from non-secure contexts. |
||||||
Issue descriptionApple proposed restricting access to loopback addresses from non-secure contexts in https://lists.w3.org/Archives/Public/public-webappsec/2016Oct/0032.html. This is in-line with the proposals in https://wicg.github.io/cors-rfc1918/ that we're experimenting with, and Mozilla seems on board as well: https://lists.w3.org/Archives/Public/public-webappsec/2016Oct/0037.html
,
Nov 18 2016
,
Sep 12 2017
This issue has been automatically relabelled type=task because type=launch-owp issues are now officially deprecated. The deprecation is because they were creating confusion about how to get launch approvals, which should be instead done via type=launch issues. We recommend this issue be used for implementation tracking (for public visibility), but if you already have an issue for that, you may mark this as duplicate. For more details see here: https://docs.google.com/document/d/1JA6RohjtZQc26bTrGoIE_bSXGXUDQz8vc6G0n_sZJ2o/edit For any questions, please contact owencm, sshruthi, larforge
,
Nov 10 2017
,
Feb 18 2018
,
Mar 3 2018
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by bugdroid1@chromium.org
, Oct 20 2016