Lucas Pardue

If you're still trying to get to grips with HTTP/3 and QUIC, this blog post includes a list of all of my Cloudflare TV segments with various deep dives and special guests.

Managing multiple paths for a QUIC connection has entered evalutation by the IESG. datatracker.ietf.org/doc/draft-ietf…

@ackriv How much is it?

Are you using Telescope to measure performance? github.com/cloudflare/tel…

『HTTPのUnencoded-Digestヘッダの提案仕様』 asnokaze.hatenablog.com/entry/2025/11/… メモ的に、ブログ書いた #asnokaze

@momoka0122y Great to see you again and hang out this week. Your English is amazing.

1週間会社を休んで英語を使う環境に身を置いてる。 1週間前より喋れるようになった気がする

@XRP369CREATOR @Cloudflare @kkblinder

Learn how a common pattern of using Go's HTTP/2 client can lead to unintended errors and the solution to avoiding them. cfl.re/4qzqfhd

We did get a Wesley Snipes gopher in there 😌

HTTP/2-based DoS attacks are here to stay. Many implementations are hardened to them. Quirky behaviour can trigger defenses and cause ENHANCE_YOUR_CALM. Read one of my latest trips down a debugging rabbit hole.

About 6 months ago Louis Navarre reached out to report some DoS-related vulnerabilities in quiche's ack processing. We fixed it up and saw no evidence that the vulnerabilities had been exploited. Check out the deep dive blog post: blog.cloudflare.com/defending-quic…

@dok2001 @janwilmake Clients' congestion window? You'd have to factor in server receive window too. Not sure on the units of tokens, packets or bytes are my lingo

@janwilmake @SimmerVigor thoughts?

cloudflare max url length is ±3200 tokens tcp congestion window is ±2870 tokens wondering if most prompts fit within this limit

Enjoying the Sumo on BBC, packed out Royal Albert Hall

A massive effort from many engineers across multiple teams. Each day we've replaced planks on the fleet of Theseus composed of the ingress proxy (TLS, QUIC and more), and the brain (FL). Our spotters in the crows nest have shouted land ahoy. The beaches are full of rustaceans.

The Internet should be private and secure by default. We’ve come a long way—but we’re not done. Next, we’re defending against tomorrow’s quantum threats 🚀

@huntharo @csswizardry @Cloudflare If Cloudflare is handling DNS, we support HTTPS RR by default

Is cloudflare handing your domain name and DNS resolution? If so they might be handling that. If you bought your domain from someone else or handle resolution with another DNS provider then it wouldn’t be automatic and you’d have to add the HTTPS record as a sibling of an A record (and can’t have it as a sibling of a CNAME record)

My site gets a staggering amount of HTTP/1.1 traffic! My latest screencast shows you how to test different protocols with @RealWebPageTest. Link in next post.

@csswizardry @Cloudflare @SpeedCurve @ackriv DM me any time :-) Real browsers by default support H2 and H3. In all likelihood the H1 traffic is automated. Good bots, bad bots, etc. IIRC you can filter/view this in the dashboards. Here's some aggregate analysis we did a couple of years ago blog.cloudflare.com/http3-usage-on…

@SimmerVigor @Cloudflare @SpeedCurve @ackriv I’m mainly trying to understand where all this H/1 stuff comes from! I may DM you at some point if that’s okay?

@csswizardry @Cloudflare @SpeedCurve Give us a shout if you'd like the Layer 4 info too #measuring-impact" target="_blank" rel="nofollow noopener">blog.cloudflare.com/new-standards/… Cc @ackriv

I wrote a @Cloudflare Worker to attach protocol information as a Server-Timing header. Then I can send that off to @SpeedCurve to compare H1 vs H2 vs H3 performance.

Super excited about this. More intel. Deeper insights. Snappier user jounrneys. Happier customers.

As a MASQUE enthusiast, I approve

We’ve deployed MoQ in production! Long time coming and first step to broader adoption

MoQ (media over quic) is a new protocol for streaming — basically pub/sub for media you can check it out running in production here → moq.dev/publish/ and the blog post (very classic cloudflare deepdive you can follow style). @rrnn is a top tier story teller

@hawkinsw Too kind Will

You should absolutely watch this presentation! @SimmerVigor is not only an expert but a skilled presenter and you will leave the talk knowing more than when you arrived!