Re: [PATCH 0 of 3] Directives for enabling http2 and http3

2023-02-08 Thread Sergey Kandaurov
> On 7 Feb 2023, at 18:50, Roman Arutyunyan wrote: > > Hi, > > Updated the patches based on latest comments. Looks good to me. -- Sergey Kandaurov ___ nginx-devel mailing list nginx-devel@nginx.org https://mailman.nginx.org/mailman/listinfo/nginx-d

[PATCH 0 of 3] Directives for enabling http2 and http3

2023-02-07 Thread Roman Arutyunyan
Hi, Updated the patches based on latest comments. -- Roman Arutyunyan ___ nginx-devel mailing list nginx-devel@nginx.org https://mailman.nginx.org/mailman/listinfo/nginx-devel

[PATCH 0 of 3] Directives for enabling http2 and http3

2023-02-01 Thread Roman Arutyunyan
Hi, Updates in this series: - Detect HTTP-level redirects to servers where the negotiated protocol is not available. Now 421 is returned. - Retained old http3 configuration for compatibility. - Reimplemented the http2 patch. Now http2 preface is read in ngx_http_wait_request_handler(). -

[PATCH 0 of 3] Directives for enabling http2 and http3

2023-01-26 Thread Roman Arutyunyan
Hi, These patches change http2 and http3 configurations. Previously, both protocols were configured by "listen" parameters: listen 8800 ssl http2; listen 8443 http3; The patches introduce new directives for configuring http2 and http3 in server scope: server { listen 8800 ssl;