fix(responseInterceptor): handle bodyless responses (HEAD/1xx/204/304) with content-encoding#1251
Conversation
…) with content-encoding
📝 WalkthroughWalkthroughThe PR fixes a bug in ChangesBodyless Response Handling
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 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 |
commit: |
fixes: #381
fixes: #658
reproduction:
response:
{ "status": 200, "text": "Error fetching proxied request: unexpected end of file", "body": {}, "headers": { "x-powered-by": "Express", "date": "Mon, 25 May 2026 10:45:02 GMT", "connection": "close", "content-length": "54" } }also mentioned in:
Summary by CodeRabbit
Bug Fixes
Tests