#Freenginx 1.27.6 has been released (#nginx / #http / #http2 / #http3 / #httpd / #Web / #Webserver / #TLS / #TLS13) https://freenginx.org/
freenginx.orgfreenginx news
Recent searches
Search options
#http3
3 posts2 participants2 posts today
#nginx 1.27.5 (dev) has been released (#http / #http2 / #http3 / #httpd / #Web / #Webserver / #TLS / #TLS13) https://nginx.org/
nginx.orgnginx
curl HTTP/3 with OpenSSL 3.5 may be coming you way soon. Tatsuhiro, the maintainer of ngtcp2, did the (unnecessarly) heavy lifting to adapt and I did the comparatively few changes for it in curl.
Once ngtcp2 releases, we can merge that hopefully for the next curl release. If you want to test, see:
GitHubngtcp2+openssl support by icing · Pull Request #17027 · curl/curl
How browsers REALLY load Web pages
When browsers load a Web page and its subresources, A LOT happens under the hood. They need to take into account render/parsing blocking resources, use a preload scanner, listen to resource hints (like preload/preconnect), loading modifiers (async/defer/module), fetchpriority, responsive images, and much more. […]
https://fosdem.org/2025/schedule/event/fosdem-2025-4852-how-browsers-really-load-web-pages/
fosdem.orgFOSDEM 2025 - How browsers REALLY load Web pages
The HTTP/3 Challenge: Bridging the Divide Between Hyperscale and Long-Tail Web Traffic
HTTP/3, built on Google's QUIC protocol, promises to revolutionize web performance, yet its adoption faces significant hurdles. As major browsers and CDNs embrace the new standard, the lack of support...
Continued thread
Scheduling HTTP Streams
by Alexander Krizhanovsky.
Understand how a web server manages millions of concurrent web requests.
* Differences in treatment for progressive JPEG vs a PNG.
* Resilient against DDoS attacks and other vulnerabilities.
* Compare Nginx, Envoy, Apache.
https://fosdem.org/2025/schedule/event/fosdem-2025-4903-scheduling-http-streams/
Live stream:
https://live.fosdem.org/watch/ua2220
Continued thread
How browsers REALLY load Web pages by Robert Marx @programmingart
Browsers go through great lengths to workaround the fact that most web servers and major CDN provides do not honour the HTTP fetch priority correctly.
The same page has a very different waterfall in Firefox, Chrome, and Safari.
https://fosdem.org/2025/schedule/event/fosdem-2025-4852-how-browsers-really-load-web-pages/
Live stream:
https://live.fosdem.org/watch/ua2220
GitHubEnable UDP GRO for QUIC by tatsuhiro-t · Pull Request #14012 · curl/curl
Yday I first talked #http3 at #webbhuset at a lovely and well organized event. Then I walked over to #securityfest where I met lots of more friends. Received so much appreciation and love all day. Gave away enormous amounts of curl stickers. Had a blast.
I'll take the train over to #Gothenburg tomorrow and talk #http3
MeetupExclusive Meetup with Daniel Stenberg creator of cURL!, Thu, May 30, 2024, 6:00 PM | MeetupOn Thursday, May 30th at 18:00, Webbhuset invites the creator of cURL, Daniel Stenberg, to our office in Gothenburg for an exclusive lecture on HTTP/3! 🤩💥
The agenda:
*
#http3 use right now:
Firefox beta 121: 28% of all HTTP
w3techs: 29.7% of the top-1M websites
Cloudflare: 30.0% of monitored web traffic
There's now an abstract provided for my #http3 talk in #Gothenburg on May 30 and even a few available seats left:
MeetupExclusive Meetup with Daniel Stenberg creator of cURL!, Thu, May 30, 2024, 6:00 PM | MeetupOn Thursday, May 30th at 18:00, Webbhuset invites the creator of cURL, Daniel Stenberg, to our office in Gothenburg for an exclusive lecture on HTTP/3! 🤩💥
The agenda:
*
Une explication détaillée de HTTP3. La principale différence est qu'il utilise UDP + QUIC + TLS au lieu de TCP + TLS.
QUIC vise à moderniser et remplacer TCP, mais pour garder une compatibilité maximale avec les équipements réseau (routeurs, firewalls, etc.) UDP est nécessaire.
https://www.smashingmagazine.com/2021/08/http3-core-concepts-part1/
Smashing Magazine · HTTP/3 From A To Z: Core Concepts — Smashing MagazineWhat exactly is HTTP/3? Why was it needed so soon after HTTP/2 (which was only finalized in 2015)? How can or should you use it? And especially, how does this improve web performance? Let’s find out.
Protocol geeks might like the new proposals on how to do #QUIC over TCP/TLS: https://datatracker.ietf.org/doc/html/draft-kazuho-quic-quic-on-streams (called Streams) and then how to do #http3 over Streams: https://datatracker.ietf.org/doc/html/draft-kazuho-httpbis-http3-on-streams
Discussed on the #HTTPbis mailing list.
IETF DatatrackerQUIC on StreamsThis document specifies a polyfill of QUIC version 1 that runs on top of bi-directional streams such as TLS. Discussion Venues This note is to be removed before publishing as an RFC. Discussion of this document takes place on the QUIC Working Group mailing list (quic@ietf.org), which is archived at https://mailarchive.ietf.org/arch/browse/quic/. Source for this draft and an issue tracker can be found at https://github.com/kazuho/draft-kazuho-quic-quic-on-streams.
I wrote about Wikipedia's HTTP/2 and SPDY deployment to its CDN and the regressions and benefits we found in page load time and other performance metrics.
It took place back in 2016, but the topic came up recently and the caveats at scale are still somewhat undocumented. Enjoy!
https://techblog.wikimedia.org/2022/11/04/http-2-performance-revisited/
techblog.wikimedia.orgHTTP/2 performance revisited – [[WM:TECHBLOG]]