You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems somewhat inevitable we might eventually want to migrate beyond HTTP/1 or require HTTP/2 for certain features (e.g., this often comes up with upload streaming). This poses a problem for localhost development (a useful location as it's a secure context) as there's no valid certificate there. Is this something we should tackle or is that the point where localhost ceases to be useful and you have to get a domain somehow?
The text was updated successfully, but these errors were encountered:
This is similar to the request recently made in OpenID to require https for local host, because it is more secure. I personally use in in production systems to access local resources. I can't image how i would do that if domain names were required.
It seems somewhat inevitable we might eventually want to migrate beyond HTTP/1 or require HTTP/2 for certain features (e.g., this often comes up with upload streaming). This poses a problem for
localhost
development (a useful location as it's a secure context) as there's no valid certificate there. Is this something we should tackle or is that the point wherelocalhost
ceases to be useful and you have to get a domain somehow?The text was updated successfully, but these errors were encountered: