Improve the traceability for denied cookies
Reported by
j.gei...@cupofsoftware.de,
Jun 21 2018
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_4) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/11.1 Safari/605.1.15 Steps to reproduce the problem: 1. Access a website hosted e.g. under http://server1.com 2. The website performs an AJAX call to http://server2.com 3. The AJAX result contains a cookie which the browser silently discards What is the expected behavior? Chrome works as expected, but an improved traceability (e.g. by setting a log-level or developer/debugger-flag) for denied cookies (e.g. a message that "A cookie X has been denied because it originated from a different domain Y for the origin X") would greatly improve the search for problems. What went wrong? I was unable to trace why the cookie I thought I received correctly was rejected by Chrome. Did this work before? N/A Chrome version: <Copy from: 'about:version'> Channel: n/a OS Version: OS X 10.13.4 Flash Version:
,
Jun 23 2018
,
Oct 12
,
Nov 14
|
||||
►
Sign in to add a comment |
||||
Comment 1 by susan.boorgula@chromium.org
, Jun 21 2018