Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

localhost domains and HTTP/2 and beyond #78

Open
annevk opened this issue Jul 10, 2020 · 2 comments
Open

localhost domains and HTTP/2 and beyond #78

annevk opened this issue Jul 10, 2020 · 2 comments

Comments

@annevk
Copy link
Member

annevk commented Jul 10, 2020

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?

@aerik

This comment has been minimized.

@TomCJones
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants