[Webkit-unassigned] [Bug 193535] [WPE][GTK] Cookies are lost when the NetworkProcess dies

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=193535

--- Comment #4 from Adrian Perez <aperez at igalia.com> ---
(In reply to Michael Catanzaro from comment #3)
> FWIW I wouldn't expect cookies to survive a network process crash. (I'm
> actually surprised to learn that WebKit is capable of restarting the network
> process at all.) [...]

There is no reason why respawning of the NetworkProcess wouldn't
work, as far as I know. If it can be done for the WebProcess,
why not for others? It strikes me as a good think to make WebKit
more resilient :)

> [...] To improve this you'd need to sync the cookie store between
> web process and UI process, which doesn't seem desirable to me.

The lifecycle of the network process is hidden way below the public API.
If a cookie is added through the API (WebKitCookieManager), next the
network process dies, when retrieving the list of cookies afterwards
it is a reasonable expectation that the list includes that one cookie.

I'll give you another example why I think that losing the cookies when
a fresh NetworkProcess starts is bad: imagine you have a WebKit based
browser on Android, where processes may be killed at any time for
backgrounded applications... you would expect that your log-ins to
websites that use cookies would continue working when you bring back
the browser to the foreground and the NetworkProcess is spawned again.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20190117/c4f97827/attachment.html>