Skip to content
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

For which 1xx responses should Set-Cookie work? #1710

Open
annevk opened this issue Sep 28, 2023 · 1 comment
Open

For which 1xx responses should Set-Cookie work? #1710

annevk opened this issue Sep 28, 2023 · 1 comment

Comments

@annevk
Copy link
Member

annevk commented Sep 28, 2023

Fetch currently requires Set-Cookie to be processed for a response whose status is 101 (though only when request's mode is "websocket") and ignored when response status is any other 1xx (or 101 and request's mode is not "websocket").

Is that the behavior we want?

Relates to httpwg/http-extensions#2084.

Credit Guoye Zhang if we end up making a change to the specification.

@mnot
Copy link
Member

mnot commented Sep 28, 2023

Current cookie spec says:

User agents MAY ignore Set-Cookie header fields contained in responses with 100-level status codes or based on its cookie policy (see Section 7.2).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants