[APPSEC-60728] Add analysis for downstream request with redirects#5347
Conversation
Typing analysisNote: Ignored files are excluded from the next sections.
|
BenchmarksBenchmark execution time: 2026-02-11 16:10:57 Comparing candidate commit f473d3e in PR branch Found 0 performance improvements and 2 performance regressions! Performance is the same for 42 metrics, 2 unstable metrics. scenario:tracing - Propagation - Trace Context
scenario:tracing - Tracing.log_correlation
|
ac7eadc to
f473d3e
Compare
|
✅ Tests 🎉 All green!❄️ No new flaky tests detected 🎯 Code Coverage 🔗 Commit SHA: f473d3e | Docs | Datadog PR Page | Was this helpful? Give us feedback! |
What does this PR do?
Add redirect follow up for downstream request analysis. RFC took quick approach to remember redirect location and for any consequent request consider it a redirect hop if its URL matches the URL of the request.
Motivation:
This is a final part of API10 RFC: Annex A.
Change log entry
Yes. Add analysis for downstream requests with redirects (+ announcement).
Additional Notes:
Announcement:
This release introduces comprehensive instrumentation for downstream HTTP requests made by your application. AppSec RASP (Runtime Application Self-Protection) now automatically instruments outbound HTTP requests made via Faraday, Excon, and RestClient.
This includes capturing request/response headers, status codes, and JSON bodies, as well as tracking redirect chains to ensure complete visibility even when requests follow multiple hops.
Body analysis can be tuned to balance security coverage with performance:
How to test the change?
CI + ST