QUIC Stream and Server Push support

D
  • 19 May '23
I noticed that QUIC Stream and QUIC Server Push support were removed in

https://hg.nginx.org/nginx-quic/rev/113e2438dbd4

And

https://hg.nginx.org/nginx-quic/rev/f742b1b46901

I'm curious on what the reasoning was, given that none was given in the commit messages?

-Dustin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20230519/a7c7c4d5/attachment.htm>
M
  • 20 May '23
Hello!

On Fri, May 19, 2023 at 06:57:04PM -0500, Dustin Marquess wrote:

> I noticed that QUIC Stream and QUIC Server Push support were 
> removed in
> 
> https://hg.nginx.org/nginx-quic/rev/113e2438dbd4
> 
> And
> 
> https://hg.nginx.org/nginx-quic/rev/f742b1b46901
> 
> I'm curious on what the reasoning was, given that none was given 
> in the commit messages?

These features weren't considered to be usable enough to be merged 
into the mainline branch, hence were removed before the merge.

For QUIC in the stream module, see this message, which provides 
detailed explanation:

https://mailman.nginx.org/pipermail/nginx/2023-April/CZ5L6KMLLZNDP2R6TGAX5MN4VLQA3U3R.html

For HTTP/3 Server Push, the main reason is that Server Push is not 
generally usable, and, in particular, not supported by browsers 
(notably, removed from Chrome, see 
https://developer.chrome.com/blog/removing-push/).  Removing 
HTTP/2 Server Push support is also planned sometime during nginx 1.25.x 
development cycle.

-- 
Maxim Dounin
http://mdounin.ru/
D
  • 20 May '23
On May 19, 2023 at 8:01 PM -0500, Maxim Dounin <mdounin at mdounin.ru>, wrote:
> Hello!
>
> On Fri, May 19, 2023 at 06:57:04PM -0500, Dustin Marquess wrote:
>
> > I noticed that QUIC Stream and QUIC Server Push support were
> > removed in
> >
> > https://hg.nginx.org/nginx-quic/rev/113e2438dbd4
> >
> > And
> >
> > https://hg.nginx.org/nginx-quic/rev/f742b1b46901
> >
> > I'm curious on what the reasoning was, given that none was given
> > in the commit messages?
>
> These features weren't considered to be usable enough to be merged
> into the mainline branch, hence were removed before the merge.
>
> For QUIC in the stream module, see this message, which provides
> detailed explanation:
>
> https://mailman.nginx.org/pipermail/nginx/2023-April/CZ5L6KMLLZNDP2R6TGAX5MN4VLQA3U3R.html
>
> For HTTP/3 Server Push, the main reason is that Server Push is not
> generally usable, and, in particular, not supported by browsers
> (notably, removed from Chrome, see
> https://developer.chrome.com/blog/removing-push/). Removing
> HTTP/2 Server Push support is also planned sometime during nginx 1.25.x
> development cycle.

Awesome, thanks!

-Dusti
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20230519/2c1deba8/attachment.htm>