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

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon May 23 11:00:29 PDT 2016


--- Comment #12 from Sam Weinig <sam at webkit.org> ---
(In reply to comment #8)
> (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?
> 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.

To be clear, the functionality in UIWebView does not actually allow for intervention in all traffic.  Notably, most traffic for video and audio assets does not get captured as it happens in mediaserverd, not the host process.

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/9d6fb805/attachment.html>

More information about the webkit-unassigned mailing list