Warn when Set-Cookie header is not stored, with reason
Reported by
d...@danielcompton.net,
Jul 25 2017
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3165.0 Safari/537.36 Steps to reproduce the problem: 1. Send a cross domain XHR POST to another origin without "With-Credentials: true" set 2. Response from other server includes "Set-Cookie" header What is the expected behavior? Chrome logs in the console a warning saying that it is not accepting the Set-Cookie header, because the request was made without "With-Credentials: true" being set. What went wrong? Chrome silently ignores the cookie, and makes no indication that it was ignored, either in the console, or even when examining the network request. Did this work before? No Does this work in other browsers? N/A Chrome version: 62.0.3165.0 Channel: canary OS Version: OS X 10.12.5 Flash Version: This is a feature request, not an issue. This is related to https://bugs.chromium.org/p/chromium/issues/detail?id=56211, as both are asking for Chrome to warn when cookies aren't accepted.
,
Jul 25 2017
,
Jul 25 2017
,
Jul 27 2017
,
Dec 14 2017
Over to network team to emit console message on web contents.
,
Dec 14 2017
Network stack doesn't know anything about devtools, so shouldn't be emitting messages to it. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by manoranj...@chromium.org
, Jul 25 2017