Skip to content

[release/9.0] Fixed devtools url used for debug with chrome and edge - #61948

Merged
wtgodbe merged 6 commits into
release/9.0from
backport/pr-61813-to-release/9.0
Oct 7, 2025
Merged

[release/9.0] Fixed devtools url used for debug with chrome and edge#61948
wtgodbe merged 6 commits into
release/9.0from
backport/pr-61813-to-release/9.0

Conversation

@github-actions

@github-actions github-actions Bot commented May 15, 2025

Copy link
Copy Markdown
Contributor

Backport of #61813 to release/9.0

/cc @javiercn @Dona278

Fixed devtools url used for debug with chrome and edge

Description

Ensures the correct creation of the devtools url with proxy to use for debug with chrome and edge browser which recently changed how urls are returned from "localhost:9222/json".

Fixes #61559

Customer Impact

Fixes a debugging issue in "debug in browser" mode.
image

Regression?

  • Yes
  • No

The format of http://localhost:9222/json changed, instead of relative uri it contains an absolute one in new browser versions.

Risk

  • High
  • Medium
  • Low

It still supports the old way, just adds an additional fallback for cases of absolute paths.

Verification

  • Manual (required)
  • Automated

Packaging changes reviewed?

  • Yes
  • No
  • N/A

@github-actions
github-actions Bot requested a review from a team as a code owner May 15, 2025 09:56
@dotnet-policy-service dotnet-policy-service Bot added this to the 9.0.x milestone May 15, 2025
@dotnet-policy-service dotnet-policy-service Bot added the pending-ci-rerun When assigned to a PR indicates that the CI checks should be rerun label May 22, 2025
@Dona278

Dona278 commented May 22, 2025

Copy link
Copy Markdown
Contributor

@javiercn courtesy ping hoping that will be merged before next net9 release 🙏

@javiercn

Copy link
Copy Markdown
Member

@Dona278 I need to check if this is already in a public .NET 10.0 release.

We normally fix things first in a preview then backport the patch. It might take an extra patch cycle as that help us reduce risk. I have triggered the PR tests to make sure that it is ready when we decide to merge it, and I'll bring it up for consideration on the next patch cycle.

@javiercn

Copy link
Copy Markdown
Member

@ilonatommy were you looking at these same E2E test failures recently?

@lewing
lewing requested a review from thaystg May 22, 2025 17:42
@thaystg

thaystg commented May 22, 2025

Copy link
Copy Markdown
Member

Will we backport to release/8.0?

@ilonatommy

ilonatommy commented May 23, 2025

Copy link
Copy Markdown
Member

@ilonatommy were you looking at these same E2E test failures recently?

yes, it got blocked on main

// [InlineData(true)] QuarantinedTest: https://github.com/dotnet/aspnetcore/issues/61882

@ilonatommy

Copy link
Copy Markdown
Member

/ba-g failure is known and not related

@ilonatommy ilonatommy removed the pending-ci-rerun When assigned to a PR indicates that the CI checks should be rerun label May 23, 2025
@ilonatommy

Copy link
Copy Markdown
Member

I see, branch protection was elevated only for main, in backports having review + Build Analysis green is not enough to merge.

@javiercn

Copy link
Copy Markdown
Member

/backport to release/8.0

@github-actions

Copy link
Copy Markdown
Contributor Author

Started backporting to release/8.0: https://github.com/dotnet/aspnetcore/actions/runs/15207479105

@javiercn

Copy link
Copy Markdown
Member

I'll leave the PR prepared, and we can make a decision

@lewing lewing added the Servicing-consider Shiproom approval is required for the issue label May 28, 2025
@ilonatommy

Copy link
Copy Markdown
Member

@lewing, the net10 equivalent fixed the issue.

@wtgodbe

wtgodbe commented Jun 4, 2025

Copy link
Copy Markdown
Member

@ilonatommy @javiercn do we need to take this one thru tactics? Ditto #62080

@javiercn

javiercn commented Jun 5, 2025

Copy link
Copy Markdown
Member

@wtgodbe yes, but I believe we are waiting for validation from a preview to bring it in.

@joperezr

joperezr commented Jun 9, 2025

Copy link
Copy Markdown
Member

Waiting on approval from Tactics to merge this

@dotnet-policy-service dotnet-policy-service Bot added the pending-ci-rerun When assigned to a PR indicates that the CI checks should be rerun label Jun 17, 2025
This was referenced Jul 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area-blazor Includes: Blazor, Razor Components feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly Servicing-approved Shiproom has approved the issue

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants