<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:pavel@salsitasoft.com" title="Pavel Zdenek <pavel@salsitasoft.com>"> <span class="fn">Pavel Zdenek</span></a>
</span> changed
<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>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">CC</td>
<td>
</td>
<td>pavel@salsitasoft.com
</td>
</tr></table>
<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#c8">Comment # 8</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:pavel@salsitasoft.com" title="Pavel Zdenek <pavel@salsitasoft.com>"> <span class="fn">Pavel Zdenek</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=138169#c5">comment #5</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=138169#c4">comment #4</a>)
> > 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?</span >
Glad to see that someone at Apple is picking this up. We even spent a TSI on asking this a long time ago. The anwser was basically "not considered a bug" so we shrugged and keep dragging the UIWebView cart.
We have built a web browser which allows for configurable intervention in the complete webview traffic, i.e. not just frames but all resources. Even XHR. The possible interventions are numerous. Cancel the request altogether, redirect, fake a response (e.g. a locally made image), tinker with outgoing or even incoming HTTP headers. It all works quite nicely on UIWebView, but it feels being left behind indeed.</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>