Closed benc-uk closed 4 years ago
Yes it just came back in the latest Windows update on Dev channel for me.
Edit: Downgrade to 1.0.3: https://github.com/microsoft/WSL/issues/9508
@illepic, @khuongduybui: If you're experiencing problems on 1.1.0 please see issue #9508. This issue covers 1.0.3 and before.
Please fill out the below information:
Your Windows build number: 10.0.18945.1001 (I am using WSL 2 mode)
What you're doing and what's happening:
Opening a URL served via a Node.js app using localhost, from a Windows browser results in page/URL never loading. It will spin indefinitely trying to load, rather than getting an error that site/page can not be found
Hitting stop and then refresh in browser will result in page loading OK Page will continue to load OK, if you send requests to it quickly, if you wait a few seconds the problem will return and the URL and site will never load
I have verified the following:
eth0
and access the app that way, I get no issuesThis seems to be a TCP socket issue with the way WSL 2 handles the new localhost bridging out to Windows
It is trivial to reproduce. Install Node.js and run the following simple server
What's wrong / what should be happening instead: HTTP request /page should instantly load
Strace of the failing command, if applicable:
NA
For WSL launch issues, please [collect detailed logs] NA
See our contributing instructions for assistance.