Clarifying the default Set-Cookie behavior.
#393
Conversation
|
Thanks for the suggestion! Aren't the two pieces of information redundant? They basically state the same thing. |
|
I agree that it's a little redundant. The first section talks about differences between The second section goes more in depth. I just wanted to copy the pattern On Mon, Sep 12, 2016 at 3:58 PM Mislav Marohnić notifications@github.com
|
| @@ -137,6 +137,8 @@ bear keeping in mind: | |||
| * By default, `fetch` **won't send any cookies** to the server, resulting in | |||
| unauthenticated requests if the site relies on maintaining a user session. | |||
|
|
|||
| * By default, the **browser will not store any cookies** set in `fetch()` responses. | |||
There was a problem hiding this comment.
Since the two bullet points are closely related, could we collapse them into one, explaining how the browser will not handle cookies at all, either sending or receiving?
I'm trying to make it clear that the
credentialsoption affects setting cookies.Perhaps this will prevent future tickets like #386