Bug 6450 seems to be reintroduced

[Vadim Yakovlev]

With current Chrome versions (tried with 58 and 59 on two different machines) the behavior described in bug 6450 seems to be reintroduced: the value of a cookie set in a response with 401 status is not respected and a previously set cookie is returned to the server instead on the following request.

C: GET resource1
S: 200, Set-Cookie: CookieName=value1

C: GET resource2, Cookie:CookieName=value1
S: 401, Set-Cookie: CookieName=value2

C: GET resource2, Cookie:CookieName=value1
...

The client should sent value2, but it sends value1.

[PhistucK]

That is a very old issue that was resolved a long, loooooong time ago. :)

You can search crbug.com for an existing open issue and star it. If you cannot find one, file a new issue using the "New issue" link on the same page.

Please, do not add a "+1" or "Me too" or "Confirmed" (or similar) comment. It just wastes the time of Chrome engineers and sends unnecessary e-mails to all of the people who starred the issue.

You can reply with a link to the found or created issue and might get triaged (and fixed) faster.

Thank you.

☆PhistucK

--
--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-discuss

---
You received this message because you are subscribed to the Google Groups "Chromium-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-discuss+unsubscribe@chromium.org.