Bug 246707 - didReceiveServerRedirectForProvisionalNavigation is not called for upgradeKnownHostsToHTTPS upgrades
Summary: didReceiveServerRedirectForProvisionalNavigation is not called for upgradeKno...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit API (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2022-10-18 13:18 PDT by Ali Juma
Modified: 2022-10-25 13:19 PDT (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ali Juma 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.
Comment 1 Radar WebKit Bug Importer 2022-10-25 13:19:19 PDT 
<rdar://problem/101558433>