fix(web-outgoing): include HTTP 303 in redirect location rewriting#119
fix(web-outgoing): include HTTP 303 in redirect location rewriting#119
Conversation
The `redirectRegex` was missing status code 303 (See Other), so `hostRewrite`, `autoRewrite`, and `protocolRewrite` did not apply to 303 responses. Upstream: http-party/node-http-proxy#1125.
|
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 (3)
✨ 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 #119 +/- ##
=======================================
Coverage 96.12% 96.12%
=======================================
Files 8 8
Lines 645 645
Branches 243 243
=======================================
Hits 620 620
Misses 24 24
Partials 1 1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Summary
redirectRegexinsetRedirectHostRewritewas missing status code 303 (See Other), sohostRewrite,autoRewrite, andprotocolRewriteoptions did not apply to 303 redirect responses.Upstream PR: http-party/node-http-proxy#1125