// network

what is JA4H HTTP-request fingerprint?

JA4H fingerprints the HTTP request itself — method, version, header order, cookie/referer presence, and Accept-Language. It requires a fingerprinting edge (not tls.peet.ws), so it is NOT YET COLLECTED in the richards seed and is carried as null honestly rather than fabricated.. Deferred to the L1 fingerprint edge; ab records null instead of guessing. Pairs with JA4 to catch tools whose TLS matches a browser but whose HTTP header order does not.