Bug 213367 - WKURLSchemeHandler does not fully implement the Http cache protocol
Summary: WKURLSchemeHandler does not fully implement the Http cache protocol
Status: RESOLVED WONTFIX
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit2 (show other bugs)
Version: Other
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2020-06-18 23:05 PDT by mali
Modified: 2020-06-20 19:24 PDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description mali 2020-06-18 23:05:51 PDT 
The current implementation of WKURLSchemeHandler only has the memory cache of http resources and no disk cache. Can the requests processed by WKURLSchemeHandler fully implement the entire Http cache protocol. WKURLSchemeHandler requires cross-process communication. If there is a disk cache, the kernel can avoid many unnecessary Cross-process data transfer to improve performance
Comment 1 Radar WebKit Bug Importer 2020-06-19 17:24:11 PDT 
<rdar://problem/64550318>
Comment 2 Alex Christensen 2020-06-19 18:59:05 PDT 
The whole point of WKURLSchemeHandler is that it is not HTTP.  If you want HTTP-like caching, you will have to implement it yourself.  It wouldn't save any Cross-process data transfers if we did because WebKit uses the network process for the HTTP disk cache.
Comment 3 mali 2020-06-20 19:24:02 PDT 
Sorry what I mean may not be in place. WKURLSchemeHandler is processed on the process of each WKWebView instance. When this process exits, the memory cache associated with it is destroyed. In other cases, WKWebView will create a  Persistent network process for WKProcessPool, at this time these cache objects will not be destroyed as the WKWebView instance exits, is this more reasonable?