#http3 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #http3, aggregated by home.social.
-
Внедрение HTTP/3 задерживается
Сетевой протокол HTTP/3 в разработке с 2016 года, а его транспорт QUIC вышел в 2013-м. На сегодняшний день оба эти стандарта поддерживаются всеми ведущими браузерами (кроме Samsung и Opera Mini) и составляют 32,5% HTTP-запросов на Cloudflare , что отражает актуальное состояние всего интернета. Но темпы внедрения HTTP/3 крайне медленные . Что же мешает веб-мастерам перейти на современный стандарт и ускорить загрузку сайтов ? Основная причина в том, что ни QUIC, ни HTTP/3 до сих пор не включены в стандартные библиотеки популярных языков программирования Go, Rust, Python и Ruby. Они не активированы по умолчанию в Node.js, веб-серверах Nginx и Apache. Прошло более десяти лет, но протокол всё ещё считается экспериментальным! Удивительно.
https://habr.com/ru/companies/ruvds/articles/1066412/
#ruvds_статьи #http3 #nodejs #quic #windows_server #миграция_соединений #мультиплексирование #rfc_9114 #0rtt
-
Firefox may bypass proxychains4 via HTTP/3 (QUIC/UDP), exposing your real IP.
Disable QUIC in about:config:
network.http.http3.enable=false
and
network.http.altsvc.enabled=false.
This forces pure TCP.
Then route Firefox through Tor SOCKS5 in proxychains4: socks5 127.0.0.1 9050.
Ensures no QUIC leaks.
#infosec #linux #tor #proxychains #privacy #quic #http3 #firefox
-
Firefox may bypass proxychains4 via HTTP/3 (QUIC/UDP), exposing your real IP.
Disable QUIC in about:config:
network.http.http3.enable=false
and
network.http.altsvc.enabled=false.
This forces pure TCP.
Then route Firefox through Tor SOCKS5 in proxychains4: socks5 127.0.0.1 9050.
Ensures no QUIC leaks.
#infosec #linux #tor #proxychains #privacy #quic #http3 #firefox
-
A public PoC now details CVE-2026-42530, an NGINX HTTP/3 RCE from a QPACK use-after-free. Upgrade to NGINX 1.31.2 to close the flaw now.
#NGINX #HTTP3 #CVE202642530 #RCE #UseAfterFree #QUIC #QPACK #PoC #Cybersecurity
-
A public PoC now details CVE-2026-42530, an NGINX HTTP/3 RCE from a QPACK use-after-free. Upgrade to NGINX 1.31.2 to close the flaw now.
#NGINX #HTTP3 #CVE202642530 #RCE #UseAfterFree #QUIC #QPACK #PoC #Cybersecurity
-
Following some discussions during #IETF last week (in the hallway and on various mailing lists), the awesome #IPvFoo extension now shows in Mozilla #FireFox if connections used H1, H2, or H3, not just IPv4-vs-IPv6! This is helpful for seeing how that angle of Happy Eyeballs works.
(It would work in the Chrome version as well but the interface for getting at this info is broken and always returns H1.)
Note that if the connection starts with H2 but then switches to H3 for later objects on the hostname (eg, if you have an Alt-Svc record) then it will show H3 rather than H2.
-
Following some discussions during #IETF last week (in the hallway and on various mailing lists), the awesome #IPvFoo extension now shows in Mozilla #FireFox if connections used H1, H2, or H3, not just IPv4-vs-IPv6! This is helpful for seeing how that angle of Happy Eyeballs works.
(It would work in the Chrome version as well but the interface for getting at this info is broken and always returns H1.)
Note that if the connection starts with H2 but then switches to H3 for later objects on the hostname (eg, if you have an Alt-Svc record) then it will show H3 rather than H2.
-
Как изменилась жизнь интернет-безопасников с приходом QUIC? IDS и threat analysing в реалиях HTTP/3
Обзорный анализ “нового” протокола HTTP/3 и подходов к анализу трафика и защите информационных систем построенных на его основе. Фингерпринтинг выступает одной из больших тем статьи, ему уделено отдельное внимание. Читать
-
А мой веб-сервер точно нормально работает?
У меня есть сервер в интернете, который работает с HTTP/2, HTTP/3, с IPv4 и IPv6… Как всё это хозяйство протестировать? Я не нашёл решение и прибёг к помощи ИИ, который мне навайбкодил нужный мне сервис. Всё это хорошо. Но, может быть из этой идеи можно слепить годный продукт или просто доработать этот? Если у вас те же проблемы с тестированием своего сайта, добро пожаловать под кат. Там я расскажу, с какой проблемой я лично столкнулся. И как, временно, решил этот вопрос.
-
Oops, I’m accidentally writing a new book on modern networking (QUIC, HTTP3, Sans-IO, etc.) There was a gap in the literature. Networking content is either a decade plus old or RFCs which aren’t always easy reads. A fundamental thread is the upending of the network layer orthodoxy to meet modern application needs.
More soon.
-
Oops, I’m accidentally writing a new book on modern networking (QUIC, HTTP3, Sans-IO, etc.) There was a gap in the literature. Networking content is either a decade plus old or RFCs which aren’t always easy reads. A fundamental thread is the upending of the network layer orthodoxy to meet modern application needs.
More soon.
-
🪧 Proxy, Record, and Mock gRPC APIs with FauxRPC: Stop writing mock stubs by hand. How FauxRPC uses smart proxying, reflection, and CEL to automate your API testing.
https://kmcd.dev/posts/fauxrpc-proxy/
#Fauxrpc #Connectrpc #Grpc #Protobuf #Api #Rpc #Go #Golang #Http3 -
🪧 Proxy, Record, and Mock gRPC APIs with FauxRPC: Stop writing mock stubs by hand. How FauxRPC uses smart proxying, reflection, and CEL to automate your API testing.
https://kmcd.dev/posts/fauxrpc-proxy/
#Fauxrpc #Connectrpc #Grpc #Protobuf #Api #Rpc #Go #Golang #Http3 -
🪧 Proxy, Record, and Mock gRPC APIs with FauxRPC: Stop writing mock stubs by hand. How FauxRPC uses smart proxying, reflection, and CEL to automate your API testing.
https://kmcd.dev/posts/fauxrpc-proxy/
#Fauxrpc #Connectrpc #Grpc #Protobuf #Api #Rpc #Go #Golang #Http3 -
𝗪𝗵𝗮𝘁 𝗶𝘀 𝗛𝗧𝗧𝗣𝟯:
https://thewhale.cc/posts/what-is-http3
What is HTTP/3? How it is Different From HTTP/2?
-
#Freenginx 1.31.2 has been released ( #nginx / #http / #http2 / #http3 / #httpd / #Web / #Webserver / #TLS / #TLS13 ) https://freenginx.org/
-
#Freenginx 1.31.2 has been released ( #nginx / #http / #http2 / #http3 / #httpd / #Web / #Webserver / #TLS / #TLS13 ) https://freenginx.org/
-
#nginx 1.31.1 (dev) has been released ( #http / #http2 / #http3 / #httpd / #Web / #Webserver / #TLS / #TLS13 / #CVE / #SecurityVulnerability ) https://nginx.org/
-
#nginx 1.31.1 (dev) has been released ( #http / #http2 / #http3 / #httpd / #Web / #Webserver / #TLS / #TLS13 / #CVE / #SecurityVulnerability ) https://nginx.org/
-
#nginx 1.30.2 has been released ( #http / #http2 / #http3 / #httpd / #Web / #Webserver / #TLS / #TLS13 / #CVE / #SecurityVulnerability ) https://nginx.org/
-
#nginx 1.30.2 has been released ( #http / #http2 / #http3 / #httpd / #Web / #Webserver / #TLS / #TLS13 / #CVE / #SecurityVulnerability ) https://nginx.org/
-
Many changes! Shipping STABLE @nlnetlabs Unbound QUIC builds aside our non QUIC variant&our cutting-edge canary builds soon! The supported architectures have been ramped up too: ppc64le, s390x, riscv64 joined the party. No own unbound.conf anymore, now we're just patching the needed #recursor settings at buildtime.
Test driving our builds verifies everything is nice. 💚
https://github.com/madnuttah/unbound-docker
#DNS #DNSSEC #DoT #DoH #QUIC #HTTP3 #Unbound #FOSS #SelfHosting #Homelab #Privacy #Security #ci #cd
-
Many changes! Shipping STABLE @nlnetlabs Unbound QUIC builds aside our non QUIC variant&our cutting-edge canary builds soon! The supported architectures have been ramped up too: ppc64le, s390x, riscv64 joined the party. No own unbound.conf anymore, now we're just patching the needed #recursor settings at buildtime.
Test driving our builds verifies everything is nice. 💚
https://github.com/madnuttah/unbound-docker
#DNS #DNSSEC #DoT #DoH #QUIC #HTTP3 #Unbound #FOSS #SelfHosting #Homelab #Privacy #Security #ci #cd
-
New canary Unbound QUIC build is out. Runs on basically any platform @nlnetlabs Unbound supports. Distroless, and built using our hardened native and mighty 🦾 OpenSSL 3.6.2 + QUIC build environment! (https://github.com/madnuttah/openssl-buildenv)
Full DNSSEC support, QUIC/HTTP3 via ngtcp2/nghttp3... So much fun!
cc @nlnetlabs 💚
https://github.com/madnuttah/unbound-docker
https://hub.docker.com/r/madnuttah/unbound
#DNS #DNSSEC #DoT #DoH #QUIC #HTTP3 #Unbound #FOSS #SelfHosting #Homelab #Privacy
-
New canary Unbound QUIC build is out. Runs on basically any platform @nlnetlabs Unbound supports. Distroless, and built using our hardened native and mighty 🦾 OpenSSL 3.6.2 + QUIC build environment! (https://github.com/madnuttah/openssl-buildenv)
Full DNSSEC support, QUIC/HTTP3 via ngtcp2/nghttp3... So much fun!
cc @nlnetlabs 💚
https://github.com/madnuttah/unbound-docker
https://hub.docker.com/r/madnuttah/unbound
#DNS #DNSSEC #DoT #DoH #QUIC #HTTP3 #Unbound #FOSS #SelfHosting #Homelab #Privacy
-
Heute kam ich endlich das zu final #http3 und #zstd #compression bei meinem #Wordpress #Blog in Betrieb zu nehmen.
Bei dem Umstieg von den sury.org Paketen auf die offiziellen #nginx Pakete gab es ein paar Probleme, wodurch ich einige Wochen ohne #http3 auskommen musste.
Ich hoffe das nun alles stabil läuft. Bisher rennt aber alles und hat #myhomezone noch einen Tick schneller gemacht.
Wer einmal testen möchte, kann gerne auf meinem #Blog vorbei schauen.
-
Lapor engkong @kongtol dan koh @semurjengkol ...
#GoToSocial :gotosocial: sama #misskey :misskey: gua lewatin #caddy biar bisa access log nya seragam di #loki. Tadinya sih mau sekalian biar bisa #http3 dari cf ke origin, tapi ternyata #cloudflared cuma support http3 dari browser ke edge doang, bukan dari edge ke origin. Tapi lumayan lah bisa http2 dari edge ke origin.
Caching juga dah gua atur di #cloudflare biar access media di #s3 full-caching.
-
🪧 ConnectRPC: Where is it now?: Reflecting on two years of ConnectRPC: How it evolved from a gRPC alternative to a complete API ecosystem.
https://kmcd.dev/posts/connectrpc-where-is-it-now/
#Connectrpc #Grpc #Protobuf #Api #Rpc #Go #Golang #Http3 #Openapi -
🪧 ConnectRPC: Where is it now?: Reflecting on two years of ConnectRPC: How it evolved from a gRPC alternative to a complete API ecosystem.
https://kmcd.dev/posts/connectrpc-where-is-it-now/
#Connectrpc #Grpc #Protobuf #Api #Rpc #Go #Golang #Http3 #Openapi -
🪧 ConnectRPC: Where is it now?: Reflecting on two years of ConnectRPC: How it evolved from a gRPC alternative to a complete API ecosystem.
https://kmcd.dev/posts/connectrpc-where-is-it-now/
#Connectrpc #Grpc #Protobuf #Api #Rpc #Go #Golang #Http3 #Openapi -
🪧 ConnectRPC: Where is it now?: Reflecting on two years of ConnectRPC: How it evolved from a gRPC alternative to a complete API ecosystem.
https://kmcd.dev/posts/connectrpc-where-is-it-now/
#Connectrpc #Grpc #Protobuf #Api #Rpc #Go #Golang #Http3 #Openapi -
Revision 709: HTTP/3 und WebTransport, mit Max Inden | Working Draft
Das war ein echt schöner Überblick über QUIC, HTTP/3, DoH und ECH. Auch immer mit einem "warum" mit schwingend.
Danke @mxinden 🙏
-
Ein Paketverlust und plötzlich steht alles? HTTP/2 über TCP leidet an Head-of-Line-Blocking. Wanderson Xesquevixos erklärt, wie #HTTP/3/QUIC das löst & wie es in #Java26 aktiviert wird.
So simpel ist der Einstieg! Jetzt lesen: https://javapro.io/de/java-26-uebernimmt-http-3-mit-der-weiterentwicklung-des-httpclient/
-
Ein Paketverlust und plötzlich steht alles? HTTP/2 über TCP leidet an Head-of-Line-Blocking. Wanderson Xesquevixos erklärt, wie #HTTP/3/QUIC das löst & wie es in #Java26 aktiviert wird.
So simpel ist der Einstieg! Jetzt lesen: https://javapro.io/de/java-26-uebernimmt-http-3-mit-der-weiterentwicklung-des-httpclient/
-
qsakaquick-send- Tired of wrestling with overly complex file transfer tools? Solution, the hidden gem of A-to-B file transfers.While alternatives like
crocandmagic-wormholeoften suffer from frustrating UX—requiring extensive manuals, relay configurations, slowness, custom scripts, and firewall tweaks—qsfocuses on simplicity and actually works.Why
qsstands out:- Zero installation: Ships as a single binary without unnecessary bloat.
- Frictionless UX: No 50-page
manpages or complex setup instructions; just run and transfer. - Reliability: Cuts out the hours of frustration and failed attempts common with over-engineered solutions.
If you need a tool that simply does exactly what it is supposed to do, check out the project and its excellent feature comparison checklist here: https://github.com/maxomatic458/quic-send
#filetransfer #datatransfer #magicwormhole #croc #quic #http3
-
via @dotnet : .NET 11 Preview 3 is now available!
https://ift.tt/BzTb5vZ
#dotnet11 #dotnet #net11preview3 #NET11Preview3 #DOTNET #ASP.NETCore #CSharp #EFCore #EntityFrameworkCore #MAUI #dotnetruntime #dotnetSDK #containerimages #webassembly #HTTP3 #systemtextjso… -
Синдром утёнка и консервативность в мышлении, чистая квинтэссенция :)
Пример вокруг HTTP/3 и того факта, что TCP-бывает ну очень сильно хуже сетевых протоколов поверх UDP, таких как QUIC.
Казалось бы, есть ведь много лет опыта использования того же MoSh, и сподвигнувшего на разработку QUIC, с целью полного и тотального отказа от TCP в мобильных сетях (сетях мобильной связи 3G/4G/5G).
Этот самый Zero RTT, оно же 0-RTT, является свойством относящимся к TLS ver.1.3, никаким боком не имеющим связи с QUIC или же HTTP/3 — более полно Zero Round Trip Time Resumption (0-RTT), настоящая притча во языцех дофига лет уже, с момента начала отказа от TLS 1.2 в пользу 1.3 версии.
Это HTTP/3 и QUIC включили в себя TLS 1.3, сделав таковой частью себя как протоколов.
1) HTTP/3 бывает и может быть только лишь на базе QUIC (никакого tcp, один только udp)
2) QUIC сам по себе как неотъемлемую часть содержит TLS 1.3, ровно в таком же виде, как и DTLS — вариант TLS для обмена данными через UDP.
Страшно представить, как у людей мозг ломается, когда узнают про TCP 2.0 в лице SCTP — насколько долго он уже существует, где и как уже много лет используется :)
Всегда несколько шалею несколько с того, как люди неглупые в техническом плане неохотно открывают для себя весьма банальные вещи в мире технологий.
#мобильные-сети #tls13 #network #network #tcp #udp #http3 #quick #lang_ru @Russia @RamSDRAdmin (R3DHX)
RE: https://mst.ramsdr.ru/@mstadmin/116255701314215548 -
🎉 Java 26 arrives, boasting "solid foundations"—because apparently, building sand castles on quicksand wasn't cutting it 😏. With groundbreaking #innovations like #HTTP3 (finally catching up to the rest of the internet) and object caching that screams "we’re almost modern!", it's clear the future is now... or maybe later 🤔. Enjoy your 40-minute nap while reading! 🛌📚
https://hanno.codes/2026/03/17/java-26-is-here/ #Java26 #ObjectCaching #FutureOfProgramming #HackerNews #ngated -
@ant0inet: Merci für den Hinweis auf das unter #CreativeCommons stehende High Performance
Browser Networking Buch aus dem #OReillyVerlag unter https://hpbn.co/! -
Warum haben deine #Microservices trotz HTTP/2 noch fiese Tail-Latenzen? Wanderson Xesquevixos zeigt, wie #Java26 mit JEP 517 HTTP/3 (QUIC) in den HttpClient bringt – inkl. Fallback.
Finde Copy-paste-Code + Logs zum Nachweisen: https://javapro.io/de/java-26-uebernimmt-http-3-mit-der-weiterentwicklung-des-httpclient/
-
Spent way too long getting HTTP/3 working on FreeBSD with nginx, so I wrote it all up.
The highlights: stock OpenSSL silently breaks QUIC at the HTTP/3 framing layer (the TLS handshake succeeds, so openssl s_client lies to you). eBPF worker routing doesn't exist on FreeBSD. And if nginx is in a jail with IPv4 NAT, a pass rule for UDP 443 is useless without a matching rdr.
New post: https://blog.hofstede.it/http3-on-freebsd-getting-quic-working-with-nginx-in-a-bastille-jail/
-
Our Mastodon instance burningboard.net now supports HTTP/3 (QUIC).
HTTP/3 replaces TCP with UDP as its transport protocol, offering lower latency and better performance, especially on lossy or low-bandwidth networks.
https://http3check.net/?host=burningboard.net
If you encounter any unexpected issues, feel free to drop me a message 🙂
-
Ein Paketverlust und plötzlich steht alles? HTTP/2 über TCP leidet an Head-of-Line-Blocking. Wanderson Xesquevixos erklärt, wie #HTTP/3/QUIC das löst & wie es in #Java26 aktiviert wird.
So simpel ist der Einstieg! Jetzt lesen: https://javapro.io/de/java-26-uebernimmt-http-3-mit-der-weiterentwicklung-des-httpclient/
-
Warum haben deine #Microservices trotz HTTP/2 noch fiese Tail-Latenzen? Wanderson Xesquevixos zeigt, wie #Java26 mit JEP 517 HTTP/3 (QUIC) in den HttpClient bringt – inkl. Fallback.
Finde Copy-paste-Code + Logs zum Nachweisen: https://javapro.io/de/java-26-uebernimmt-http-3-mit-der-weiterentwicklung-des-httpclient/