3 ms·
Perhaps browsers could include a "legacy mode" where stuff behind an IPv4 NAT could still be accessible over HTTP. This would of course require all manner of wa
by IgorPartola 12y ago
Perhaps browsers could include a "legacy mode" where stuff behind an IPv4 NAT could still be accessible over HTTP. This would of course require all manner of warnings. In general though, my router has a self-signed cert and works over HTTPS. I can even load my own cert. OpenWRT FTW.
- rogerbinns 12y ago> This would of course require all manner of warnings Ok, now try and word one of those so that regular folk understand what the heck it is saying. And your "legacy mode" means HTTP is still supported. There is nothing wrong with deprecating HTTP over bare TCP, but being completely unsupported in the near future is unworkable. Everyone including this effort is about a slow steady migration.