fix(test-server): bind to 127.0.0.1 instead of 'localhost'#40295
fix(test-server): bind to 127.0.0.1 instead of 'localhost'#40295yury-s wants to merge 1 commit intomicrosoft:mainfrom
Conversation
'localhost' resolution is ambiguous on dual-stack systems and prefers '::1' first on many environments. The IPv6 loopback has proven unreliable (recent Windows 25H2 update broke it outright for the Playwright VS Code extension), leaving clients with connect ETIMEDOUT ::1:<port>. Default both the test-server CLI --host option and the internal startHttpServer helper to IPv4 loopback, so clients can always connect. Fixes: microsoft#40226
pavelfeldman
left a comment
There was a problem hiding this comment.
stale defender rules problem
Test results for "MCP"26 failed 6395 passed, 976 skipped Merge workflow run. |
Test results for "tests 1"1 failed 7 flaky39248 passed, 847 skipped Merge workflow run. |
|
I don't know how to address this anywhere, but in an on going effort to replace ipv4 this seems like a step backwards? |
Summary
test-server --hostandstartHttpServerto127.0.0.1instead oflocalhost.localhostresolves to::1first on many dual-stack setups; the Windows 11 25H2 update broke IPv6 loopback outright, leaving clients withconnect ETIMEDOUT ::1:<port>(widely reported for the VSCode extension).--host ::1explicitly.Fixes #40226