Match and inspect JA4 fingerprints

Stream now shows a JA4 Fingerprint field for HTTPS and HTTP/3 requests, and the rule editor can match that fingerprint. Use it alongside IP, ASN, user agent, and path conditions to investigate or respond to groups of clients with similar TLS behavior.

Cleartext HTTP requests have no JA4 fingerprint. Requires FlowGuard Proxy v0.7.1 or newer. See the JA4 fingerprint guide for matching examples.