fix(middleware): do not append duplicate x-forwarded-* header values#120
fix(middleware): do not append duplicate x-forwarded-* header values#120
Conversation
Preserve existing x-forwarded-* headers instead of appending proxy values. When a request already carries these headers from a downstream proxy, the old code would concatenate them (e.g. "10.0.0.1,192.168.1.2") causing incorrect multi-hop attribution. Now the headers are only set when absent, matching expected reverse-proxy behavior. Upstream: http-party/node-http-proxy#1581
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #120 +/- ##
=======================================
Coverage 96.12% 96.12%
=======================================
Files 8 8
Lines 645 645
Branches 243 241 -2
=======================================
Hits 620 620
Misses 24 24
Partials 1 1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Summary
x-forwarded-for,x-forwarded-port, andx-forwarded-protoheaders instead of appending proxy-computed valuesweb-incoming.ts) and WebSocket (ws-incoming.ts) middleware"10.0.0.1,192.168.1.2") causing incorrect multi-hop attributionUpstream: http-party/node-http-proxy#1581
Test plan
web-incomingandws-incomingXHeaders passes