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

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=138169

            Bug ID: 138169
           Summary: WKWebView does not fully support custom NSURLProtocol
    Classification: Unclassified
           Product: WebKit
           Version: 528+ (Nightly build)
          Hardware: iOS
                OS: Unspecified
            Status: NEW
          Severity: Blocker
          Priority: P2
         Component: WebKit2
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: carlos at adaptive.me

Summary:
It was possible to install a custom NSURLProtocol to handle requests from UIWebView. This is no longer possible with WKWebView - the NSURLProtocol subclass *does* receive the +canInitWithRequest: message, but is never instantiated. 


Steps to Reproduce:
1. Create and register a custom NSURLProtocol subclass that handles all requests.
2. Create a WKWebView and load a request.


Expected Results:
The custom NSURLProtocol subclass should receive a +canInitWithRequest: message, and then an instance should be created and initialized with -initWithRequest:cachedResponse:client:.


Actual Results:
The NSURLProtocol subclass *does* receive the +canInitWithRequest: message, but is never instantiated.


Version:
iOS 8.0, iOS 8.0.1, iOS 8.1 (tested)


Notes:
This breaks any behind the scenes encryption, compression, interception, caching, etc. This is breaking many things and blocking the adoption of WKWebView.


Configuration:
All emulators and devices with >= iOS 8 support.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20141029/756585ce/attachment-0002.html>