Localhost connection not private for swagger pages

[bmikusfrost]

Developing some stuff with ASP.Net and using Swagger to interact with the API, but since latest version (6.7.3329.17) I get a page saying "Your connection is not private" without any option to progress. Running the swagger page in private window works fine, but I would prefer to not have to open a private window every time I need to test the API.

Is there a configuration that would allow me to still see the page even though Vivaldi says it is not private?

[yngve]

@bmikusfrost "Not private" usually refers to a TLS certificate that does not chain to a known root, or an accepted certificate. Private window probably shouldn't be able to view it, either, without clicking through the advanced step.

[Zalex108]

@bmikusfrost

Hi,
Welcome to Vivaldi's Forum

You might need to:

Enable:

• chrome://flags/#temporary-unexpire-flags-m122
• chrome://flags/#temporary-unexpire-flags-m123

Restart

• chrome://flags/#unsafely-treat-insecure-origin-as-secure

Disable:

• chrome://flags/#https-upgrades
• chrome://flags/#https-first-mode-for-typically-secure-users

--
Avoid Data loss
Follow the Backup | Reset links below

---

Vivaldi Backup | Reset + Extra Steps

[bmikusfrost]

@yngve Well, the advanced step does not allow to view the page on the regular window. But I do agree, that a non-private page should be a warning on a private window as well, with a button that allows the user to risk it.

[yngve]

@bmikusfrost IIRC if the advanced step is not enabled, then there is a serious issue (such as revocation of the certificate) involved, there should be more information about the actual problem in the dialog

[bmikusfrost]

@yngve interesting.

Well, in any case, my particular issue got resolved. I think ASP.net did something in the background to setup a cert locally, and it took a moment for that to propagate. A recent run of the swagger page did not trigger any issues.

Thanks for the replies!

[AdmissionBangla]

This post is deleted!

[DoctorG]

@AdmissionBangla localhost hostname can not have a valid SSL connection at all.
hostname localhost is not a valid domain for SSL certificates.
That's why your explanation is completely wrong.

[micaljhone]

This post is deleted!

[marapavelka]

Doesn't work. There are no chrome://flags/#temporary-unexpire-flags-m122, chrome://flags/#temporary-unexpire-flags-m123 and chrome://flags/#https-upgrades

[DoctorG]

@marapavelka I do not know Swagger, but you could try these Vivaldi flags:

• chrome://flags/#allow-insecure-localhost
  Enable
• chrome://flags/#unsafely-treat-insecure-origin-as-secure
  Enable
  Add http://127.0.0.1 to text field