fix(responseInterceptor): prevent trailer/content-length conflict#1249
Conversation
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughresponseInterceptor removes ChangesTrailer Header Handling
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 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: |
Causing this error to be thrown:
```shell
node:_http_outgoing:522
throw new ERR_HTTP_TRAILER_INVALID();
^
Error [ERR_HTTP_TRAILER_INVALID]: Trailers are invalid with this transfer encoding
```
---------
Co-authored-by: zibo <ziboilihua@gmail.com>
da3bad3 to
93cf883
Compare
Causing this error to be thrown:
node:_http_outgoing:522 throw new ERR_HTTP_TRAILER_INVALID(); ^ Error [ERR_HTTP_TRAILER_INVALID]: Trailers are invalid with this transfer encodingcloses #830
Summary by CodeRabbit