4 ms·
How does it behave when the site nominally supports https but only uses a self signed cert? Many local network items are like this. in most cases it might be be
by birdman3131 6y ago
How does it behave when the site nominally supports https but only uses a self signed cert? Many local network items are like this. in most cases it might be better to fallback to http but I am not sure.
- ocdtrekkie 6y agoFWIW, it is rapidly becoming the right choice to operate an internal trusted certificate authority, as browsers aggressively push HTTPS. In part, because this is now needed to monitor your own network traffic at the edge.
- louis-lau 6y agoIt's mentioned in the blog post, the link to which you're commenting on.
- CGamesPlay 6y agoI think what will happen is that visiting `vcap.me` will open `https://vcap.me https://vcap.me`, which would fail with a cert error, so Chrome will automatically (without showing the error) open `http://vcap.me http://vcap.me`, which would issue a redirect to `https://vcap.me https://vcap.me`, which would fail with a cert error. If you were navigating to `localhost`, Chrome would directly open `http://localhost http://localhost` which would do the redirect. It's unclear if Chrome is smart enough to know that `vcap.me` is a localhost service, but we can imagine a remote host which would behave the same way.