Testing 0-RTT is working correctly

I read through the 2017 blog on the 0-RTT QUIC support and enabled it on a test site, but I am not getting the header CF mentioned (Cf-0rtt-Unique) Is it still an expected header? The page is correctly using HTTP/3 and on both Chrome and Firefox appears to be using 0-RTT one the second reloads of the pages as the TLS negotiation is 0. Is this header still expected? Anyway to check outside of wireshark?
0 Replies
No replies yetBe the first to reply to this messageJoin