> 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
>> 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
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
