http://localhost is considered mixed content
Reported by
raniel...@gmail.com,
Aug 9 2017
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.31 Safari/537.36 Steps to reproduce the problem: According to https://sites.google.com/a/chromium.org/dev/Home/chromium-security/security-faq?pli=1#TOC-Which-origins-are-secure- it has the following: Which origins are "secure"? Secure origins are those that match at least one of the following (scheme, host, port) patterns: (https, *, *) (wss, *, *) (*, localhost, *) (*, 127/8, *) (*, ::1/128, *) (file, *, —) (chrome-extension, *, —) It states that localhost is considered a secure origin, but chrome on all platforms doesn't treat it as such. What is the expected behavior? *://localhost/ should be treated as secure What went wrong? get security errors Did this work before? N/A Chrome version: 61.0.3163.31 Channel: beta OS Version: 10.0 Flash Version: https://bugs.chromium.org/p/chromium/issues/detail?id=362214 indicated that this was fixed at one point.
,
Aug 9 2017
,
Aug 9 2017
Yes, both issues are exactly what we encountered.
,
Aug 9 2017
,
Aug 9 2017
,
Aug 14 2017
This looks like issue with http://localhost,In-house(TE)team not having the permission to create localhost(scheme, host, port), hence adding the respective label for it to triage further. Thank You!
,
Oct 5 2017
,
Oct 5 2017
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by est...@chromium.org
, Aug 9 2017Components: Blink>SecurityFeature>SecureContexts
Labels: OS-Android OS-Chrome OS-Linux OS-Mac
Summary: http://localhost is considered mixed content (was: http://localhost/ is not considered secure)