<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - WKWebView does not fully support custom NSURLProtocol"
href="https://bugs.webkit.org/show_bug.cgi?id=138169#c14">Comment # 14</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - WKWebView does not fully support custom NSURLProtocol"
href="https://bugs.webkit.org/show_bug.cgi?id=138169">bug 138169</a>
from <span class="vcard"><a class="email" href="mailto:ignacio@backbase.com" title="Ignacio Calderon <ignacio@backbase.com>"> <span class="fn">Ignacio Calderon</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=138169#c11">comment #11</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=138169#c6">comment #6</a>)
> > In my particular case, this interception is needed for 2 main purposes:
> > 1. Implement SSL pinning for web view content (most important)
> > 2. Provide encrypted on-device assets, and be able to decrypt them before
> > pass them to the web view for rendering.
>
> Is this for resources with the http/https scheme? Or a different scheme?</span >
For (1), https resources.
For (2), main case file:// and optionally http*://. The assets could be on the app bundle encrypted to avoid tampering or reverse engineering, and accessed via file:// schemes. Or http/https equivalent to an end-to-end encryption, to dynamically update the content.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>