<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:drew@sealedabstract.com" title="drew@sealedabstract.com">drew@sealedabstract.com</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>drew@sealedabstract.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#c24">Comment # 24</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:drew@sealedabstract.com" title="drew@sealedabstract.com">drew@sealedabstract.com</a>
</span></b>
<pre>We use NSURLProtocol to actually use a non-HTTP(S) wire protocol. It's more efficient than the traditional stuff and provides a real UX improvement for various classes of captive native/web applications.
A lot of the usecases in this thread could (in theory) be resolved by new API surface–content blocking, cookies, etc could all be solved by new API.
However, for folks who actually need to intercept the requests themselves, the existing API was very good, and it's a real shame to see it go.</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>