search

unbit / uwsgi

uWSGI application server container
http://projects.unbit.it/uwsgi
Other
3.45k stars 687 forks source link

HTTP/2 #1269

Open jerzyk opened 8 years ago

jerzyk commented 8 years ago

will it be supported? what timeframe do you plan for it?

Chrome is already disabled their support for SPDY and newest versions do not even try to negotiate SPDY

There are some good http/2 libraries - maybe use them (https://nghttp2.org/) ?

unbit commented 8 years ago

I think the best thing we can do now is listing (maybe directly here) the available http/2 libraries and choose the one that fit best in the current codebase.

The current spdy code got basically no coverage so i am seriously thinking to discard it

jerzyk commented 8 years ago

such a list was already made https://github.com/http2/http2-spec/wiki/Implementations in my opinion nghttp2 looks promising

unbit commented 8 years ago

I am about to start a router-nghttp2 branch with the objective of using its parser (even for http/1.1) while maintaining all of the router-http features

marc1n commented 6 years ago

Any progress in this subject?

est commented 6 years ago

I think uWSGI as a h2 gateway would be awesome!

LuGHuaaa commented 5 years ago

Any progress in this subject?

chienjchienj commented 4 years ago

Any progress in this subject?

erichanson commented 3 years ago

Would love to see http/2 support in uWSGI!

mangelozzi commented 6 months ago

Are you guys not using a reverse proxy like Nginx?

If yes, then it doesn't matter if uWSGI itself does not support HTTP/2, as long as it is placed behind a reverse proxy like Nginx that does support HTTP/2. In a common web application architecture, Nginx acts as the front-facing server that handles client connections, including managing HTTP/2 connections, and then forwards the requests to backend servers like uWSGI via a protocol that the backend supports (such as HTTP/1.1, uwsgi, FastCGI, etc.).

jerzyk commented 6 months ago

and what is purpose of your comment?

http2 here allows you to use http/2 features that otherwise will not be there !

simply because http/2 will be terminated before and http/1 or 1.1 will be passed to the backend - loosing all benefits of http/2

this is far more than e.g. ssl termination

e.g. how would you do a server push (e.g. image or css) from the server to client?

intgr commented 6 months ago

Note that the uwsgi project readme states:

Note: The project is in maintenance mode (only bugfixes and updates for new languages apis)

So don't get your hopes up, builtin HTTP/2 support probably isn't coming.

e.g. how would you do a server push (e.g. image or css) from the server to client?

FWIW many webservers can interpret Link: response HTTP headers and convert them to server push, such as Nginx: https://www.nginx.com/blog/nginx-1-13-9-http2-server-push/#automatic-push

jerzyk commented 6 months ago

FWIW many webservers can interpret Link: response HTTP headers and convert them to server push

sure, same with sendfile headers... buth those are some kind of workarounds...

maintenance mode

yes, this is sad, but without financial backing/sponsoring it is more and difficult to maintain open source projects... soon (with async projects on the raise) uwsgi will be obsolete