-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HTTP Header, HTTP Network and Session Fingerprints #320
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #320 +/- ##
==========================================
+ Coverage 84.30% 84.52% +0.22%
==========================================
Files 144 144
Lines 6746 6941 +195
Branches 3102 3179 +77
==========================================
+ Hits 5687 5867 +180
- Misses 389 400 +11
- Partials 670 674 +4
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
BenchmarksBenchmark execution time: 2024-07-18 14:02:51 Comparing candidate commit 1162a90 in PR branch Found 8 performance improvements and 1 performance regressions! Performance is the same for 10 metrics, 0 unstable metrics. scenario:bool_equals_matcher.random
scenario:float_equals_matcher.random
scenario:ip_match_matcher.random
scenario:is_xss_matcher.random
scenario:regex_match_matcher.case_insensitive_flag.random
scenario:regex_match_matcher.case_insensitive_option.random
scenario:regex_match_matcher.lowercase_transformer.random
scenario:signed_equals_matcher.random
scenario:unsigned_equals_matcher.random
|
23ee838
to
2ab351c
Compare
This PR introduces the HTTP header, HTTP network and session fingerprint processors, taking advantage of functionality introduced in #318. To include these processors, one must add the following configuration:
These fragments are specifically aimed at providing information regarding the headers used to access the application:
Finally note that both network and header processors currently evaluate the same set of headers, unfortunately due to the nature of processors it's not possible to evaluate all headers only once, however I'm evaluating options...
Related Jiras: