[release/6.0] [wasm][debugger] Fix (chrome|edge)://inspect for the debug proxy #65219
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
|
Tagging subscribers to this area: @thaystg |
|
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsBackport of #65216 to release/6.0 The chrome://inspect CDP logic is rejecting /cc @lewing Customer ImpactWithout this change the official browser debugger front end is no longer able to connect properly to proxy preventing customers from using chrome or edge as the debugger frontend. TestingManual testing. RiskVery low. Simply sets the content-length in the response header
|
rbhanda
added
Servicing-approved
|
can someone with the appropriate authorization please merge this? |
|
PR has sign-off, the |
ghost
locked as resolved and limited conversation to collaborators
Backport of #65216 to release/6.0
The chrome://inspect CDP logic is rejecting
/jsonresponses that don't include the content length in the response, this fixes that and allows chrome://inspect to connect to the proxy properly/cc @lewing
Customer Impact
Without this change the official browser debugger front end is no longer able to connect properly to proxy preventing customers from using chrome or edge as the debugger frontend.
Testing
Manual testing.
Risk
Very low. Simply sets the content-length in the response header