Nginx 1.26 Released With Experimental HTTP/3 Support

[phoronix]

Phoronix: Nginx 1.26 Released With Experimental HTTP/3 Support

Nginx 1.26 stable is out as the newest version of this popular alternative to the Apache web server while also able to work as a load balancer, reverse proxy, and HTTP cache. Nginx 1.26 incorporates the great work from the Nginx 1.25 mainline branch such as experimental HTTP/3 support...

https://www.phoronix.com/news/nginx-1.26-Released

[ahrs]

The ngx_http_v3_module is used and relies on having an SSL library present with QUIC support.

Is this all sorted with OpenSSL and in distributions repositories now? The last time I looked at this things were a mess and you were better off compiling with an out-of-tree version of BoringSSL.

[Artim]

Is this all sorted with OpenSSL and in distributions repositories now? The last time I looked at this things were a mess and you were better off compiling with an out-of-tree version of BoringSSL.

Nginx for some reason writes something about v1.1.1, my last information is that QUIC support is on a good path in the latest version of v3.x but it's not fully there yet.

[numacross]

Is this all sorted with OpenSSL and in distributions repositories now? The last time I looked at this things were a mess and you were better off compiling with an out-of-tree version of BoringSSL.

Unfortunately it's still a mess, especially if you care about high performance. HAProxy's SSL support status page describes the current situation in detail.

[aerospace]

freenginx has also been updated to version 1.26

[dlq84]

If there is HTMLX and not javascript SO needed, if there is React or similar tags like in the XML format and TypeScript definitions seems not so easy to define and use, seems Google ideas that WebGPU computation is still not as stream or stack, fifo. Maybe think that declaring some document, sending that document to GPU, to network with attached VSCode something and returned back is still possible with today's software. But http is not gopher, now is webworkers or similar network stack and document definition in head is not saying such configuration or is not declared where it could be found or some restrictions on it.

document streaming then could be also GPU based and frames from GPU document streaming to Monitor document maybe with some attached helper libs to simplify thinking is not so http/3 designed when http today could be almost anything and http lost its declaring power when won the protocol race but the technology race madness missing and libwebkit is only part of equation not so Wanted

wat?...

[S.Pam]

If you want http3 that's not a beta solution you can try Caddy instead. Works really well and is very performant.

[botipua22]

i moved from nginx to caddy because of the single config file. all major web servers seem to be mature and do their job well (yes, even apache httpd).

[rene]

updated: https://t2sde.org/packages/nginx

[moonwalker]

wat?...

Graphorrhea, perhaps?