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

HTTP2 is enabled by default #90

Closed
ernado opened this issue Jun 5, 2015 · 5 comments
Closed

HTTP2 is enabled by default #90

ernado opened this issue Jun 5, 2015 · 5 comments
Assignees

Comments

@ernado
Copy link

ernado commented Jun 5, 2015

Why?

It is enabled here and configured here

Maybe it is more expected to enable http2 when TLS key pair is present, because http2 without TLS is unusable in current implementation?

@ernado
Copy link
Author

ernado commented Jun 5, 2015

dub of #89

@vishr vishr closed this as completed Jun 5, 2015
@vishr vishr reopened this Jun 5, 2015
@vishr vishr self-assigned this Jun 5, 2015
@ernado
Copy link
Author

ernado commented Jun 5, 2015

Proposal:
Use http2 by default only with TLS
If user specifies explicitly to use http2, use it http mode as well as https
If user specifies explicitly to not use http2, dont use it at all.

This will solve possible issue when go implementation of http2 will support h2c (issue on http2 repo)

@vishr
Copy link
Member

vishr commented Jun 5, 2015

@ernado Thanks for your suggestions, I will consider them while making the change. In general, I am not very convinced about not allowing HTTP2 over TCP, there is already a PR pending but looks like it won't make it to the library. I would like to see HTTP2 being used for internal services where TLS is not needed.

For reference:

bradfitz/http2#59
bradfitz/http2#48

@ernado
Copy link
Author

ernado commented Jun 5, 2015

@vishr I would realy like to use h2c too.
I think that h2c can make it to the library, but it will be not enabled by default. There is no reason to forbid using HTTP2 over TCP at all.

@vishr
Copy link
Member

vishr commented Jun 5, 2015

Perfect, will do the changes at next opportunity.

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

No branches or pull requests

2 participants