fix: pass full response headers in net module#21552
Conversation
nornagon
left a comment
There was a problem hiding this comment.
What other kinds of filtering is Chromium doing here? Is it doing any sort of normalization that we might not want to lose? Do we only need the set-cookie headers here?
The raw headers are populated from Currently I'm only aware the |
|
@nornagon Can you take another look at this? |
4f020aa to
7bb4e08
Compare
7bb4e08 to
da40732
Compare
|
Release Notes Persisted
|
|
I have automatically backported this PR to "8-x-y", please check out #21769 |
|
I have automatically backported this PR to "7-1-x", please check out #21770 |
Description of Change
Close #20631.
Use raw headers instead of filtered headers in net module. This is a regression caused by network service refactoring.
Checklist
npm testpassesRelease Notes
Notes: Fix
set-cookieheader not passed in net module.