-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
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
Standardize access to cookie headers #4
Comments
There's a proposal to add |
This is already being solved in the upstream fetch spec: whatwg#1346. |
just popping in this little side note: whatwg#1384 if a CookieStore could maybe perhaps serve as an alternative solution. of sending/reading cookies |
Note, there is a spec now for |
Indeed, with the addition to |
As outlined at WHATWG/fetch there is often the need in a server environment to access cookie headers.
For example editing Cookie headers:
Headers.prototype.getAll
would solve this problem, but was removed from the browser specification. Should we standardize on adding it back? Or should we define a new method all together? Ideally we should align withnode-fetch
andundici
as well.The text was updated successfully, but these errors were encountered: