NEW 246707
didReceiveServerRedirectForProvisionalNavigation is not called for upgradeKnownHostsToHTTPS upgrades 
https://bugs.webkit.org/show_bug.cgi?id=246707
Summary didReceiveServerRedirectForProvisionalNavigation is not called for upgradeKno...
Ali Juma
Reported 2022-10-18 13:18:14 PDT
When a navigation is upgraded to https as a result of upgradeKnownHostsToHTTPS being enabled, the embedder does not get any navigation callback for this implicit redirect. While these upgrades are not actually server redirects, the existing didReceiveServerRedirectForProvisionalNavigation seems like the most straightforward way to notify an embedder, without having to introduce new public API in WKNavigationDelegate. Without any callback, embedders only see an unexplained URL change, and it seems fragile to assume this is a redirect of an existing navigation.
Attachments
Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2022-10-25 13:19:19 PDT
<rdar://problem/101558433>
Note You need to log in before you can comment on or make changes to this bug.