WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
138736
Appcache is still downloaded in the WebProcess
https://bugs.webkit.org/show_bug.cgi?id=138736
Summary
Appcache is still downloaded in the WebProcess
Carlos Garcia Campos
Reported
2014-11-14 02:29:18 PST
This causes that http/tests/appcache/auth.html times out, because the authentication happens in the network process, but the manifest is downloaded in the web process and the authentication challenge happens.
Attachments
Add attachment
proposed patch, testcase, etc.
Alexey Proskuryakov
Comment 1
2014-11-14 15:11:13 PST
It's not just the manifest, all appcache entries are downloaded in WebProcess too.
Carlos Garcia Campos
Comment 2
2014-11-15 00:31:49 PST
(In reply to
comment #1
)
> It's not just the manifest, all appcache entries are downloaded in > WebProcess too.
Right! btw, what's the plan for all the things that are currently loaded using ResourceHandle directly? I mean, should they go through the resource scheduler, or do we need new internal API to send these requests to the network process? I can help with this.
Alexey Proskuryakov
Comment 3
2014-11-15 01:06:48 PST
I do not have a design ready, and each of these may need different approaches. It depends on how much functionality is shared with normal resource loading (e.g. do we need to send a referrer, do we need document's cookies, do we need to cancel requests when navigating away, do we need any prioritization). For appcache in particular, we could consider moving the whole thing out to NetworkProcess, not only network loading aspect. PingLoader and CSP reporting (which reuses PingLoader) may be the easiest ones to start with.
Claudio Saavedra
Comment 4
2018-05-28 08:57:44 PDT
I'm going to close this because it's not timing out anymore..
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug