Issue metadata
Sign in to add a comment
|
Custom DNS pages redirected to https
Reported by
bastian....@googlemail.com,
Dec 11 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.84 Safari/537.36 Example URL: Steps to reproduce the problem: 1. Setup an environment with custom DNS (eg. *.dev) 2. Try accessing these pages via http What is the expected behavior? What went wrong? The browser is redirecting to https Did this work before? Yes Chrome version: 63.0.3239.84 Channel: stable OS Version: Ubuntu 16.04 Flash Version: Tried on different pcs. (Linux and Windows) It happens after the latest update.
,
Dec 12 2017
The issue seems to be out of TE-scope as it is related to setting up an environment using DNS server. Hence, adding label TE-NeedsTriageHelp for further investigation from dev team. Thanks...!!
,
Dec 12 2017
Related bug 793994 .
,
Dec 12 2017
Hi bastian.rihm@googlemail.com, thanks for the report. Are you accessing this page using localhost? Could you provide more details on your setup? Can you provide a chrome://net-export Log by following the instructions at https://sites.google.com/a/chromium.org/dev/for-testers/providing-network-details ?
,
Dec 12 2017
,
Dec 12 2017
This is due to HSTS preloading of the .dev TLD. .dev is a real TLD, not for use in local testing. You can use one of the TLDs described in RFC 2606 to avoid collisions with possible future domains: .test .example .invalid .localhost
,
Dec 12 2017
Is bug 793994 is duplicate of this bug too?
,
Dec 12 2017
Re #7: It's likely a duplicate. If we can confirm the localhost urls that they use are of .dev TLD.
,
Dec 12 2017
Issue 793994 has been merged into this issue.
,
Dec 12 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by krajshree@chromium.org
, Dec 12 2017