Open yarosman opened 9 months ago
I understand that raw ja3 fingerprint contains greased/resumption information which is benefit for waf/antibot. But I still think this requirement is similar/dupicated with https://github.com/phuslu/nginx-ssl-fingerprint/issues/42 and https://github.com/phuslu/nginx-ssl-fingerprint/issues/13 , because ja4/cisco also intend to solve it.
It looks like much easier to add ja3 raw supporting than ja4/cisco implementation ))
It would be great to allow to get raw ja3 fingeprint