[Webkit-unassigned] [Bug 138169] WKWebView does not fully support custom NSURLProtocol
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon May 23 10:52:47 PDT 2016
https://bugs.webkit.org/show_bug.cgi?id=138169
--- Comment #10 from Sam Weinig <sam at webkit.org> ---
(In reply to comment #9)
> (In reply to comment #5)
> > (In reply to comment #4)
> > > Are there any plans on implementing this functionality? I'd really love to
> > > use WKWebView, but this limitation forces me to keep using the UIWebView.
> >
> > We are investigating it, but it would really help us to understand more
> > about why you were using this functionality. What type of loads did you need
> > to intercept?
>
> Some things we would like to do with WKWebView that are currently impossible
> due to no ability to intercept and modify loading behaviour:
Thanks! A few additional questions:
>
> * HTTPS Everywhere - Detect HTTP loads of resources in a whitelist, modify
> them to become HTTPS loads
> * Content blocking - Block resources, both top level and resource loads
Diving into these, are you doing dynamic analysis of of loads, or would a static matching / modification engine suite these needs? (Similar to the Content Blocker feature in WebKit, though not exposed as API, but with the ability to modify requests in addition to blocking).
> * Better control over headers - Ability to look and modify headers, both
> incoming and outgoing
What are the use cases you have for these? Which headers do you need to you want to modify and why?
> * Implement custom content caching and content preloading - Need the ability
> to take over a resource load and provide our own response
What is the use case for this?
> * Better control of cookies. Currently there is no way to control cookie
> policy in WKWebView, this is trivial to imlement if we can control network
> requests
Which aspects of the cookie policy do you want to control? What are the use cases for it?
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20160523/7d7bbe72/attachment.html>
More information about the webkit-unassigned
mailing list