| Summary: | Incorrect SSL error code received from WKWebView | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Eugene But <eugenebut> | ||||
| Component: | WebKit2 | Assignee: | Nobody <webkit-unassigned> | ||||
| Status: | RESOLVED INVALID | ||||||
| Severity: | Normal | CC: | ap, stuartmorgan | ||||
| Priority: | P3 | Keywords: | InRadar | ||||
| Version: | 528+ (Nightly build) | ||||||
| Hardware: | iPhone / iPad | ||||||
| OS: | All | ||||||
| Attachments: |
|
||||||
This was determined to be an issue outside WebKit. It's tracked internally as rdar://problem/18517043. Eugene, you filed multiple bugs today, do you know if any of these are also in Radar? If they are, could you please annotate these with Radar links? All filled issues were filed to Apple Radar. Radar ID: 18517043. |
Created attachment 244191 [details] Test app Summary: webView:didFailProvisionalNavigation:withError: passes NSURLErrorServerCertificateUntrusted error if user clock is not set correctly Steps to Reproduce: 1. Set device time to past (f.e. year 2007) 2. Unarchive, build and run SSLCertTest on device 3. Observe console log Expected Results: Console log is "Certificate is untrusted" Actual Results: Console log should be either "Certificate has bad date" or "Certificate is not yet valid". User should be given a hint that something either wrong with the clock or certificate has expired.