4 ms·

> install your own root cert on client devices... That’s a pain in the ass just to test a local website.

• Ajedi32 9y ago
  If you're just testing on localhost, there should be no need for a cert. As the article says, localhost is treated the same as https here. In the future, I expect all features that require a secure context will start treating localhost as secure, if they don't already.
  • hungerstrike 9y ago
    I usually have 2 or 3 devices that I need to test a website on, so no - localhost alone doesn't help at all. For example: I run the website on my workstation and I want to test it on my iOS and Android devices. With this recommendation, I have to generate a certificate and install it everywhere just to test simple functionality. Since Google recommended the ".test" domain for internal testing that's what I use. In the past I had used ".dev" (now owned by Google) and ".local" (now used by Apple for bonjour networking) to setup test domains on my LAN. So, Google should allow these features through for ".test" at least. Honestly, they should make it a flag that developers can toggle at the very, very least.
    • Ajedi32 9y ago
      --unsafely-treat-insecure-origin-as-secure="http://example.com" http://example.com" https://www.chromium.org/Home/chromium-security/deprecating-powerful-features-on-insecure-origins https://www.chromium.org/Home/chromium-security/deprecating-... Or just use a self-signed cert and click though the security warning.
      • hungerstrike 9y ago
        The first recommendation doesn't work on iOS or Android. The second, well, who knows if it will work today or tomorrow. And, it's still a pain in the ass.