Bug 138736
| Summary: | Appcache is still downloaded in the WebProcess | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Carlos Garcia Campos <cgarcia> |
| Component: | WebKit2 | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | ap, csaavedra |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Carlos Garcia Campos
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
It's not just the manifest, all appcache entries are downloaded in WebProcess too.
Carlos Garcia Campos
(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
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
I'm going to close this because it's not timing out anymore..