4 ms·
A lot of browsers already expect tls to enable specific features. I've had things break between dev and prod because of a lack of tls on the backend as well. I
by gravypod 6y ago
A lot of browsers already expect tls to enable specific features. I've had things break between dev and prod because of a lack of tls on the backend as well.
It's also one of those things that once you sort it out it's no longer a problem. Like "why do I need to setup all this complex stuff to manage a dependancy? Just give me your source code and let me `gcc -o binary a.c b.c ....`"
In reality once you solve a problem with an ergonomic solution and the solution improves your alignment with production and comes at no real cost it's a win/win/win.
- tialaramex 6y agoMostly browsers require Secure Context rather than TLS, so http://127.0.0.1/ http://127.0.0.1/ which is a secure context is fine.