Skip to content

Commit 3739795

Browse files
waldekmastykarzCopilot
andcommitted
feat(blog): add post for Dev Proxy v2.3.2 release with fixed Chrome DevTools inspection
Co-authored-by: Copilot <copilot@github.com>
1 parent b69259b commit 3739795

2 files changed

Lines changed: 48 additions & 0 deletions

File tree

public/blog/images/v2-3-2.png

477 KB
Loading
Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
---
2+
title: "Dev Proxy v2.3.2 with fixed Chrome DevTools inspection"
3+
description: "Dev Proxy v2.3.2 fixes Chrome DevTools inspection broken on Chromium 146+ (Chrome and Edge) by updating the WebSocket connection to use the IPv4 loopback address."
4+
date: 2026-04-23
5+
author: "Waldek Mastykarz, Garry Trinder"
6+
tags: ["release"]
7+
image: "/blog/images/v2-3-2.png"
8+
---
9+
10+
We've just released **Dev Proxy v2.3.2** - a patch release that fixes Chrome DevTools inspection broken on Chromium 146+.
11+
12+
### **In this version:**
13+
14+
- Fixed **DevToolsPlugin** WebSocket connection failing on Chromium 146+ (Chrome and Edge)
15+
16+
### **Fixed Chrome DevTools inspection**
17+
18+
If you use the **DevToolsPlugin** to inspect intercepted requests in Chrome DevTools, you may have noticed that the WebSocket connection stopped working after updating Chrome or Edge to version 146 or later. DevTools would open but fail to connect, leaving you unable to inspect requests:
19+
20+
![Chrome DevTools WebSocket connection error](https://private-user-images.githubusercontent.com/1331392/581223512-0e7bfaee-b88e-470a-8024-c9c59ef91d59.png)
21+
22+
The issue? Starting with Chromium 146, the browser resolves `localhost` differently for WebSocket connections. Dev Proxy's internal WebSocket server was binding to `localhost`, which no longer worked reliably with the updated Chromium network stack.
23+
24+
**What changed:**
25+
26+
We updated the WebSocket server and the DevTools inspector URL to use the IPv4 loopback address (`127.0.0.1`) instead of `localhost`. This small but important change restores full compatibility with Chromium 146+ while continuing to work with older browser versions.
27+
28+
Thanks to [@AndresAFaes](https://github.com/AndresAFaes) for reporting the issue and contributing the fix, and to [@MarcusKohnert](https://github.com/MarcusKohnert) for bringing it to our attention!
29+
30+
## Dev Proxy Toolkit
31+
32+
[Dev Proxy Toolkit](https://marketplace.visualstudio.com/items?itemName=garrytrinder.dev-proxy-toolkit) is an extension that makes it easier to work with Dev Proxy from within Visual Studio Code. Alongside the new release of Dev Proxy, we've also released a new version of the toolkit, v1.20.0.
33+
34+
In this version, we've:
35+
36+
- Updated all JSON snippets to use v2.3.2 schemas
37+
38+
Checkout out the [changelog](https://marketplace.visualstudio.com/items/garrytrinder.dev-proxy-toolkit/changelog) for more information on changes and bug fixes.
39+
40+
### **Why upgrade to v2.3.2?**
41+
42+
**Working DevTools inspection** - Chrome and Edge DevTools connect reliably again on Chromium 146+
43+
44+
### **Try it now**
45+
46+
Download **Dev Proxy v2.3.2** today and build better API-connected applications with confidence!
47+
48+
Got feedback or ideas? [Join us](https://github.com/dotnet/dev-proxy/discussions) and be part of the conversation.

0 commit comments

Comments
 (0)