We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Since .getSetCookie() was introduced, HeaderList has an additional .cookies field, which is not updated on .clear():
.getSetCookie()
HeaderList
.cookies
.clear()
undici/lib/fetch/headers.js
Lines 95 to 98 in 816dcaa
This is observable:
const req1 = new undici.Request('http://localhost', { headers: { 'set-cookie': 'a=1' } }); console.log([...req1.headers]); // --> [ [ 'set-cookie', 'a=1' ] ] const req2 = new undici.Request(req1, { headers: {} }); console.log([...req2.headers]); // --> [] console.log(req2.headers.getSetCookie()); // --> [ 'a=1' ] - unexpected!
The text was updated successfully, but these errors were encountered:
Can you provide a code sample that uses undici.fetch & a node http server?
edit: nvm I misread it
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Since
.getSetCookie()
was introduced,HeaderList
has an additional.cookies
field, which is not updated on.clear()
:undici/lib/fetch/headers.js
Lines 95 to 98 in 816dcaa
This is observable:
The text was updated successfully, but these errors were encountered: