[Webkit-unassigned] [Bug 138169] WKWebView does not fully support custom NSURLProtocol
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Tue May 24 04:31:16 PDT 2016
https://bugs.webkit.org/show_bug.cgi?id=138169
Daniel <danielo at opera.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |danielo at opera.com
--- Comment #15 from Daniel <danielo at opera.com> ---
Hello guys,
Following up the discussion:
https://lists.webkit.org/pipermail/webkit-dev/2016-May/thread.html#28241
I'd like to share some use cases I have for this feature.
Opera on iOS implements a custom HTTP(S) protocol to do:
1. Data savings (see http://www.opera.com/turbo ). This greatly improves connectivity under crappy network conditions for millions of users. It's especially important for people in countries which can only dream about 4G.
2. Peer-to-peer inobtrusive security. For that we collect bits of site security information that is only available via low-level network APIs.
3. Presenting sites as icons (and grouping multiple pages into the same icons). For that we hook into the HTML data stream to parse meta data ASAP. In addition we intercept and react on HTTP redirects. This is a part of the http://operacoast.com app identity.
4. Progress loading reporting, automatic retries on bad networks. For that we do traffic QoS monitoring.
5. Fast going back and offline content. That is controlled partially by a custom cache, and partially in NSURLProtocol.
6. Ad-blocking.
Almost all of what Stefan Arentz says and other mentioned applies to us as well, as the need for: untrusted resources blocking, custom cache, content preloading, certificate pinning, HSTS.
With that said, it's so important feature to have for my team that
we are staying with WebKit1 for now.
See also:
https://bugs.webkit.org/show_bug.cgi?id=137299
https://bugs.webkit.org/show_bug.cgi?id=137302
https://bugs.webkit.org/show_bug.cgi?id=138131
--
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/20160524/4c6694aa/attachment.html>
More information about the webkit-unassigned
mailing list