Re: HTTP/2 Gateway

2015-12-15 Thread Nicholas Capo
> Can you name such applications that are only able to talk HTTP/2? The developers I support would like to use GRPC [1] which is HTTP/2 only. I need to provide an HA/LB system to support them. I'm not saying this would be easy to implement, only that I need it :-) Thank you for your help, Nichol

Re: HTTP/2 Gateway

2015-12-15 Thread CJ Ess
I think what they are asking is to support the transport layer so that they don't have to support both protocols on whatever endpoint they are developing. Maybe I'm wrong and someone has grand plans about multiplexing requests to an upstream with http/2, but I haven't seen anyone ask for that expl

Re: HTTP/2 Gateway

2015-12-15 Thread Valentin V. Bartenev
On Monday 14 December 2015 18:24:01 Nicholas Capo wrote: > My specific use case is to support an HTTP/2 application behind a load > balancer (reverse proxy). > > Also as a backend LB between services that could use a long running HTTP/2 > connection to do their communication. > > Places where I n

Re: HTTP/2 Gateway

2015-12-14 Thread Nicholas Capo
My specific use case is to support an HTTP/2 application behind a load balancer (reverse proxy). Also as a backend LB between services that could use a long running HTTP/2 connection to do their communication. Places where I need an LB, but also know that both ends would /prefer/ to use HTTP/2.

Re: HTTP/2 Gateway

2015-12-14 Thread Maxim Dounin
Hello! On Mon, Dec 14, 2015 at 09:57:02AM -0800, Frank Liu wrote: > "multiplexing" seems to be a good use case for upstream proxying. We don't > have control how fast end users adopting HTTP/2, so we may still have tons > of HTTP/1.x requests coming in, but we can certainly upgrade upstream > ser

Re: HTTP/2 Gateway

2015-12-14 Thread Valentin V. Bartenev
On Monday 14 December 2015 09:57:02 Frank Liu wrote: > "multiplexing" seems to be a good use case for upstream proxying. We don't > have control how fast end users adopting HTTP/2, so we may still have tons > of HTTP/1.x requests coming in, but we can certainly upgrade upstream > servers that we co

Re: HTTP/2 Gateway

2015-12-14 Thread Frank Liu
"multiplexing" seems to be a good use case for upstream proxying. We don't have control how fast end users adopting HTTP/2, so we may still have tons of HTTP/1.x requests coming in, but we can certainly upgrade upstream servers that we control to support HTTP/2. If nginx upstream proxy module can a

Re: HTTP/2 Gateway

2015-12-14 Thread Maxim Dounin
Hello! On Fri, Dec 11, 2015 at 10:03:15PM +, Nicholas Capo wrote: > Is HTTP/2 proxy support planned for the near future? Short answer: No, there are no plans. Long answer: There is almost no sense to implement it, as the main HTTP/2 benefit is that it allows multiplexing many requests wi

Re: HTTP/2 Gateway

2015-12-11 Thread Nicholas Capo
Is HTTP/2 proxy support planned for the near future? Nicholas On Sun, Dec 6, 2015 at 8:14 PM Maxim Dounin wrote: > Hello! > > On Sun, Dec 06, 2015 at 03:00:23PM +0100, bjun...@gmail.com wrote: > > > i've tried to use nginx as http/2 gateway for backends which only >

Re: HTTP/2 Gateway

2015-12-06 Thread Maxim Dounin
Hello! On Sun, Dec 06, 2015 at 03:00:23PM +0100, bjun...@gmail.com wrote: > i've tried to use nginx as http/2 gateway for backends which only > supporting HTTP 1.1. If a backend is already HTTP/2 ready, than HTTP/2 > should be used. > > When i test my configuration (simple p

HTTP/2 Gateway

2015-12-06 Thread bjun...@gmail.com
Hi, i've tried to use nginx as http/2 gateway for backends which only supporting HTTP 1.1. If a backend is already HTTP/2 ready, than HTTP/2 should be used. When i test my configuration (simple proxy_pass / upstream), the connection from nginx to the backend is always HTTP 1.1 (even i