[release/8.0] [Blazor] each navigation to external logs 2 errors a minute later

[github-actions]

Backport of #53271 to release/8.0

/cc @javiercn

[Blazor] each navigation to external logs 2 errors a minute later

Capture an exception and log a message when navigation fails because the session has ended.

Description

• The user clicks the link to the target URL.
• That link is intercepted in the JavaScript.
• .NET is called to determine if navigation to the URL needs to be prevented.
• It is determined that there is no need to prevent navigation and "navigateTo" is called via JS interop in NavigationManager.ts.
• The URL is determined to be external by "navigateTo" and the location is set to the new URL.
• The unload event in the browser is automatically triggered, which in turn triggers the call to _disconnect.
• As a result, the promise to "navigateTo" never completes (the page gets unloaded before that) and the associated task in .NET ends up getting cancelled with a timeout.

Fixes #45267

Customer Impact

Customers see a large number of errors in their logs when their sites contain links to external sites, which in turn can trigger alerts in their incident monitoring systems.

Regression?

• Yes
• No

Risk

• High
• Medium
• Low

The scenario in which the issue happens is well defined and the fix is simple.

Verification

• Manual (required)
• Automated

Packaging changes reviewed?

• Yes
• No
• N/A

---

When servicing release/2.1

• Make necessary changes in eng/PatchConfig.props

[ghost]

Hi @github-actions[bot]. If this is not a tell-mode PR, please make sure to follow the instructions laid out in the servicing process document.
Otherwise, please add tell-mode label.

[ghost]

Hi @github-actions[bot]. Please make sure you've updated the PR description to use the Shiproom Template. Also, make sure this PR is not marked as a draft and is ready-to-merge.

To learn more about how to prepare a servicing PR click here.

[ghost]

Hi @github-actions[bot]. This PR was just approved to be included in the upcoming servicing release. Somebody from the @dotnet/aspnet-build team will get it merged when the branches are open. Until then, please make sure all the CI checks pass and the PR is reviewed.