3 ms·
IP addresses and localhost are still exempt from these changes. For development purposes, nothing serious should change; localhost is already a secure context.
by jeroenhd 6y ago
IP addresses and localhost are still exempt from these changes. For development purposes, nothing serious should change; localhost is already a secure context.
I'd very much watch out for using automated tools like these. Many browsers do not check certificate revocation and this leaves your browser open to some extensive MitM attacks. If you use this, you should probably create a second profile (firefox /p to create and pick one) so your normal browsing won't be affected.
In my opinion, it's easier to just type "thisisunsafe" into the warning page once if you use it for developing. If you're demoing your application, putting it on a server with a Let's Encrypt cert shouldn't be too hard either.
I'm sure this has its uses, but I just can't figure out what they would be if you do not wish to take huge security risks.