Making _certificateChain API public will simplify implementation of security UI (https lock) for web browsers. In WebKit nightly build webView:didReceiveAuthenticationChallenge:completionHandler: provides certs chain. However it is not called on every navigation. It means that if app needs to know the certs of current page it has to maintain persistent cache: host-name: cert-chain. The certs are already cached by WebKit, so storing this cache twice is additional overhead. rdar://21342465
webView:didReceiveAuthenticationChallenge:completionHandler: does not provide information about the frame which loads a resource. Hence caching certs, so they can be reused later for lock icon is not viable. Without certificateChain public API correct implementation of security lock is not possible.
Created attachment 255301 [details] Add a certificateChain property to WKWebView
Created attachment 255327 [details] Add a certificateChain property to WKWebView Revised to make the property non-nullable
Fixed in <http://trac.webkit.org/r185876>.