Issue metadata
Sign in to add a comment
|
Set-Cookie header is not exposed to onHeadersReceived callback
Reported by
ay.mesh...@gmail.com,
Oct 24
|
||||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.67 Safari/537.36 Steps to reproduce the problem: 1. Create a simple extension that listens for onHeadersReceived callbacks 2. Navigate through websites and compare headers received by the callback and what you see in the developer tools 3. Set-Cookie is never present What is the expected behavior? What went wrong? Set-Cookie header must be present in the responseHeaders array It works okay in the stable and beta versions of Chrome, though. Did this work before? N/A Does this work in other browsers? N/A Chrome version: 72.0.3590.0 (Official Build) canary (64-bit) Channel: canary OS Version: OS X 10.14.0 Flash Version:
,
Oct 25
,
Oct 25
Reporter@ - Thanks for filing the issue...!! Could you please provide a sample test file/url to test the issue from TE-end. This will help us in triaging the issue further. Thanks...!!
,
Oct 25
I believe this is a regression from having network service enabled. Can you try disabling the experiment from chrome://flags/#network-service and confirm that it works?
,
Oct 26
,
Oct 26
> Can you try disabling the experiment from chrome://flags/#network-service and confirm that it works? You're right, the issue is gone after I disable it.
,
Oct 26
This is a known behavior difference with the network service enabled. We decided not to support modifying Set-Cookie with webRequest after verifying it was not used very much (or at all) in the wild, see issue 827582 . If you need to modify cookies, there is also the chrome.cookies API that may be useful: https://developer.chrome.com/extensions/cookies
,
Oct 26
To be clear, this isn't about modifying the cookies, it is just about viewing it. It seems odd for a webRequest consumer that this header would be missing, but I can follow-up on that other bug thread!
,
Oct 26
Also, it appears that this is not just about cookies, check this thread: https://bugs.chromium.org/p/chromium/issues/detail?id=827582#c21 |
|||||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||||
Comment 1 by dtapu...@chromium.org
, Oct 24