[Webkit-unassigned] [Bug 246707] New: didReceiveServerRedirectForProvisionalNavigation is not called for upgradeKnownHostsToHTTPS upgrades

[bugzilla-daemon at webkit.org]

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

            Bug ID: 246707
           Summary: didReceiveServerRedirectForProvisionalNavigation is
                    not called for upgradeKnownHostsToHTTPS upgrades
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebKit API
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: ajuma at chromium.org
                CC: achristensen at apple.com, beidson at apple.com,
                    cdumez at apple.com

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.

-- 
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/20221018/cfe28773/attachment.htm>