Re: Routing based on ALPN

2018-03-13 Thread Roman Arutyunyan
Wiktor, On Wed, Mar 07, 2018 at 12:38:51PM +0100, Wiktor Kwapisiewicz via nginx wrote: > > below is the initial version of patch that creates the > > "$ssl_preread_alpn_protocols" variable; the content is a comma-separated > > list of protocols, sent by client in ALPN extension, if present. > > >

Re: Routing based on ALPN

2018-03-07 Thread Maxim Konovalov
On 07/03/2018 14:38, Wiktor Kwapisiewicz via nginx wrote: [...] > This looks *very good*, thanks for your time! Thanks for your testing, Wiktor. -- Maxim Konovalov ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: Routing based on ALPN

2018-03-07 Thread Wiktor Kwapisiewicz via nginx
> below is the initial version of patch that creates the > "$ssl_preread_alpn_protocols" variable; the content is a comma-separated > list of protocols, sent by client in ALPN extension, if present. > > Any feedback is appretiated. > I have just tested this patch and can confirm it's working per

Re: Routing based on ALPN

2018-03-06 Thread Vladimir Homutov
On Sun, Feb 25, 2018 at 08:16:18PM +0100, Wiktor Kwapisiewicz via nginx wrote: > >> Is there a way to access and save ALPN value to a variable? > > > > It should possible to parse the incoming buffer with > > https://nginx.org/r/js_filter and create a variable to make a routing > > decision on. >

Re: Routing based on ALPN

2018-02-25 Thread Wiktor Kwapisiewicz via nginx
>> Is there a way to access and save ALPN value to a variable? > > It should possible to parse the incoming buffer with > https://nginx.org/r/js_filter and create a variable to make a routing > decision on. > Excellent idea for quickly solving this problem, thanks! Would a long term solution

Re: Routing based on ALPN

2018-02-19 Thread Konstantin Pavlov
On 19/02/2018 14:02, Wiktor Kwapisiewicz via nginx wrote: > Hello, > > I'm looking for a way to route traffic on port 443 based on ALPN value > without SSL termination. > > ssl_preread_module [1] does something similar but the only exposed > variable ($ssl_preread_server_name) is for SNI, not ALP

Re: Routing based on ALPN

2018-02-19 Thread Vladimir Homutov
On Mon, Feb 19, 2018 at 12:02:06PM +0100, Wiktor Kwapisiewicz via nginx wrote: > Hello, > > I'm looking for a way to route traffic on port 443 based on ALPN value > without SSL termination. > > ssl_preread_module [1] does something similar but the only exposed > variable ($ssl_preread_server_name)

Routing based on ALPN

2018-02-19 Thread Wiktor Kwapisiewicz via nginx
Hello, I'm looking for a way to route traffic on port 443 based on ALPN value without SSL termination. ssl_preread_module [1] does something similar but the only exposed variable ($ssl_preread_server_name) is for SNI, not ALPN. A bit of context. I'd like to use nginx to host regular HTTPS server