Issue metadata
Sign in to add a comment
|
Network service prevents remembering login across sessions
Reported by
khym.cha...@gmail.com,
Sep 6 2017
|
||||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.79 Safari/537.36 Steps to reproduce the problem: 1. Set your profile to restore previous tabs on startup. 2. Set chrome://flags/#network-service to "disabled" and restart browser 3. Got to any YouTube video and log in. 4. Set chrome://flags/#network-service to "Enabled" and restart browser What is the expected behavior? You'll still be logged into YouTube when the browser restarts. What went wrong? You won't be logged into YouTube when the browser restarts. Did this work before? N/A Chrome version: 61.0.3163.79 Channel: stable OS Version: Fedora 25 Flash Version: Shockwave Flash 26.0 r0 * If you try to log into YouTube while network service is enabled the login will work, so it doesn't prevent loggin in entirely. * If you set network service back to disabled and then restart the browser without trying to log in, when the browser is back up you'll be logged in again, so they cookies aren't being cleared or deleted. * The same problem happens with pixiv.net
,
Sep 6 2017
Maybe it is related to cookies?
,
Sep 6 2017
It's almost certainly related to cookies. That sounds very much like the two instances (network-service disabled and network-service enabled) are using different persistent cookie stores. Having said that, while I know that when the network service is enabled there's a NetworkContext around that doesn't have a persistent cookie store, I also thought it wasn't used for much, and specifically it wouldn't be used for requests generated by a renderer. Matt, is there something about the high level structure of backing storage for cookies in the enable/disable network service context I'm missing?
,
Sep 6 2017
The network service only uses in-memory cookie store for now, which is why this isn't working. Note to reporter: network service is not production ready, so this is mostly meant for developers to test out. No need to file bugs.
,
Sep 6 2017
Ah. Perhaps I should file an RFE that chrome://flags should indicate which flags shouldn't get bug reports.
,
Sep 6 2017
It's way too early to be filing this sort of bug. The on disk cookie store isn't even hooked up to the network service yet.
,
Sep 6 2017
In general, you probably shouldn't be filing bugs for features under about:flags - they're disabled by default for a reason.
,
Sep 19 2017
,
Nov 7 2017
Apologies, applied the wrong component in bulk. |
|||||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||||
Comment 1 by yzshen@chromium.org
, Sep 6 2017Components: Internals>Network>Service