New — Iris AI drafts your firewall, routing & rate-limit rules. Explore AI features →
Changelog
Security

Match clients by their HTTP/2 fingerprint

The Traffic Inspector shows each HTTP/2 request's fingerprint and each HTTP/3 request's JA4, and any rule can match req.h2_fingerprint, req.ja4 or conn.ja3.

Match clients by their HTTP/2 fingerprint

A scripted client can copy a browser's user agent, but its TLS and HTTP/2 handshakes still give it away. The edge already worked out each client's TLS fingerprint, JA4, and showed it in the Traffic Inspector. A client's HTTP/2 settings and first frames are just as telling, and you couldn't see them or write a rule on them.

Now the Traffic Inspector shows each HTTP/2 request's fingerprint, and any traffic rule can match it. Above, Acme Labs blocks the client that copies its product prices: it sends a browser's user agent, but its HTTP/2 fingerprint gives it away, and one Custom Response rule answers it 403 on the product pages.

The request details of a POST to /v1/orders over HTTP/2 in the Traffic Inspector: Bot score 92 Browser, TLS fingerprint (JA4) and HTTP/2 fingerprint 1:65536;2:0;4:6291456;6:262144|15663105|0|m,a,s,p, each with a copy button
A browser's request: its HTTP/2 fingerprint sits next to its JA4. The scraper's is different, which is all the rule needs.

What changed

  • In the Traffic Inspector. A request that came over HTTP/2 shows its HTTP/2 fingerprint next to its TLS fingerprint (JA4), with a copy button.
  • In every rule. A rule's condition, and any ${...} value, can read req.h2_fingerprint, req.ja4 and conn.ja3. Over HTTP/1.1 and HTTP/3 a request has no HTTP/2 fingerprint, and req.h2_fingerprint is empty.
  • A JA4 over HTTP/3 too. A request over HTTP/3 now shows its TLS fingerprint (JA4) as well. It starts with q, for QUIC, where a JA4 over HTTP/1.1 or HTTP/2 starts with t, and a Bot Management rule checks it against its JA4 lists.
  • With Bot Management. The fingerprints come with the Bot Management feature, the same one as the Bot Management rule.

Get started

  1. Open the Traffic Inspector, click a request that came over HTTP/2, and copy its HTTP/2 fingerprint.
  2. Open the endpoint's Traffic Policy tab and click Add Rule next to on_http_request.
  3. Choose a rule, for example Custom Response with status 403, and set its Condition: req.h2_fingerprint == "<the fingerprint>".
  4. Add && req.path.startsWith("/v1/products") to keep it to the pages that client scrapes.
  5. Read the docs: Fingerprints in any rule.

Read the docs

Ask an AI to summarise this page
Deploy
App hosting Edge functions Domains & certificates
Connect
Secure tunnels API gateway Multi-region edge
Protect
Bot protection & challenge WAF & firewall Edge login
Observe & AI
Monitoring Inspector & replay Iris AI MCP server AI Gateway
Developers
Developer tools Docs ngrok policy converter Blog Changelog
Compare
Ngris vs ngrok Ngris vs Cloudflare Tunnel Ngris vs Vercel Ngris vs Netlify Expose localhost guide
More
Solutions Pricing Enterprise Sign in Get Started Free