It’s mind-boggling to me the hoops we have to jump through to get https://localhost working for #web #development.
Browsers should just show a pop-up: “Are you a web developer using https://localhost for testing? If so, we’ll treat it as trusted. If you don’t know what this means, answer No. [Yes, No]”
And boom. If you answer yes, you can test with https://localhost without requiring mkcert, certutil, etc.
(Until then, you can use https://codeberg.org/small-tech/auto-encrypt-localhost in your #NodeJS projects.)
@aral Hmm. What would the usecase be for localhost HTTPS in the first place? AFAIK the HTTPS-only feature restrictions already don't apply for localhost.
@joepie91 Some do, some don’t. If you want to make sure you don’t get any surprises during production, it’s best to make your development environment match your production environment as much as possible.
@joepie91 @aral Sometimes it's the code itself which checks whether it is running under https and tries to redirect from http to https on the same hostname.