Skip to content

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented May 23, 2025

Backport of #61948 to release/8.0

/cc @javiercn @github-actions[bot]

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

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 23, 2025 09:52
@dotnet-policy-service dotnet-policy-service bot added this to the 8.0.x milestone May 23, 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 Jun 4, 2025
@maraf maraf changed the title [release/8.0] [release/9.0] Fixed devtools url used for debug with chrome and edge [release/8.0] Fixed devtools url used for debug with chrome and edge Jun 6, 2025
HarrisonSlater added a commit to HarrisonSlater/Harri.SchoolDemoAPI.BlazorWASM that referenced this pull request Jul 27, 2025
Target net10, for now  (WASM debugging is currently broken in 8, 9, pending dotnet/aspnetcore#62080
@ilonatommy
Copy link
Member

/azp run

@ilonatommy ilonatommy added Servicing-consider Shiproom approval is required for the issue and removed pending-ci-rerun When assigned to a PR indicates that the CI checks should be rerun labels Sep 18, 2025
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@javiercn
Copy link
Member

@lewing @wtgodbe this can go through tactics any time now and get merged on the next patch cycle. @ilonatommy validated things.

@ilonatommy ilonatommy added area-blazor Includes: Blazor, Razor Components feature-blazor-wasm This issue is related to and / or impacts Blazor WebAssembly labels Sep 18, 2025
@ilonatommy ilonatommy added Servicing-approved Shiproom has approved the issue and removed Servicing-consider Shiproom approval is required for the issue labels Sep 19, 2025
@ilonatommy
Copy link
Member

@wtgodbe, this one also got approved.

Copy link
Contributor

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.

Copy link
Contributor

Looks like this PR hasn't been active for some time and the codebase could have been changed in the meantime.
To make sure no conflicting changes have occurred, please rerun validation before merging. You can do this by leaving an /azp run comment here (requires commit rights), or by simply closing and reopening.

@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 Sep 26, 2025
@ilonatommy ilonatommy removed the pending-ci-rerun When assigned to a PR indicates that the CI checks should be rerun label Sep 29, 2025
@ilonatommy
Copy link
Member

/azp run

Copy link

Azure Pipelines successfully started running 3 pipeline(s).

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.

4 participants