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

Add support for HTTP/2 #251

Open
divs1210 opened this issue Jun 2, 2016 · 2 comments
Open

Add support for HTTP/2 #251

divs1210 opened this issue Jun 2, 2016 · 2 comments

Comments

@divs1210
Copy link

@divs1210 divs1210 commented Jun 2, 2016

Netty 4.1 onwards support HTTP/2. Here's an example of a server.

@ztellman

This comment has been minimized.

Copy link
Owner

@ztellman ztellman commented Mar 10, 2017

This is a very highly voted feature request, so I just want to explain why it hasn't been worked on yet.

  • There are perfectly good HTTP/2 proxies which provide most of the protocol upside without any changes to the application server
  • Certain features which don't lend themselves to proxies, such as "server push" of related content, aren't part of the core Ring spec, and I don't have a strong opinion as to how the spec should be extended

Given both of these, this is a ways down my list of useful features to add to Aleph. If anyone has counterarguments against these, or additional points to raise, please feel free to comment on this thread.

@thheller

This comment has been minimized.

Copy link
Contributor

@thheller thheller commented Nov 10, 2017

I have a use case where HTTP/2 support would be very useful.

There are several HTTP server instances shadow-cljs (build tool for CLJS). All for development purposes. One for each browser build that just serves the static files and one "shared" server which handles the websocket connections used by the REPL clients. It is also used to live-reload files in a browser env.

I just added support for SSL in development since a few people asked for it.

It would be very neat if I could just turn on HTTP/2 as well. Don't need things like server-push.

Not a high priority since it works just fine without. Given that :none development builds easily download a couple hundred .js files HTTP/2 would be very beneficial.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.