[Webkit-unassigned] [Bug 138169] WKWebView does not fully support custom NSURLProtocol

[bugzilla-daemon at webkit.org]

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

--- Comment #9 from Stefan Arentz <stefan at arentz.ca> ---
(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:

* 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
* Better control over headers - Ability to look and modify headers, both incoming and outgoing
* Implement custom content caching and content preloading - Need the ability to take over a resource load and provide our own response
* 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

Giving developers access to the URL loading system opens the door to work around many WKWebView limitations. The WKWebView APIs are extremely shallow, not giving us enough room to customize. But a lot of requests that developers have can be solved if access to networking/request loading is available.

(We are building a browser, Firefox for iOS, but many of our wishes are pretty common and have valid use cases in 'normal' WKWebView usage too)

-- 
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/5569ae39/attachment-0001.html>