Files served over internal network are cut off

[saschagehlich]

• A brief description

Since upgrading to the latest Insider Preview, I can't seem to get any webserver serving a larger file (in my case an unminified build of React.JS of 685KB). The file seems to be cut off at some random point.

• Expected results

I'd expect a curl to a file on a local server (running with python -m SimpleHTTPServer) to return the whole file.

• Actual results (with terminal output if applicable)

$ curl "http://localhost:8082/build/js/vendor/react.js"
# ... prints some file contents ...
curl: (18) transfer closed with 170392 bytes remaining to read

(Remaining byte count varies)

• Your Windows build number
  Insider Preview 14965

• Steps / All commands required to reproduce the error from a brand new installation
  Place some larger file in a directory, run python -mSimpleHTTPServer 8082. Then open another terminal, run curl http://localhost:8082/myfile.js. Similar issues occur when running a server using node-static, except that the curl process just hangs at some random point (connection stays open).

[aseering]

Hi @saschagehlich -- could you take a look at #610 ? I think it's the same issue. If so, it has actually been around since probably the initial WSL release, but it's a race condition so some change may have made it worse on your machine.

[saschagehlich]

Hey @aseering, thanks for replying. I just did a fresh reinstall which did not help unfortunately. Not sure if the issue is related since I'm also not able to load any files using Chrome on Windows from a SimpleHTTPServer server running WSL right now. If I use node-static, I at least get some response, before it stops mid-file and keeps loading indefinitely. node-static is also reporting "Request contains invalid range header: [ '612152', '612152' ]".

While typing this response, I tried downloading another browser (Firefox) which does not work either (Chrome reports "Network error"). I also can't download any larger files via Edge ("This file couldn't be downloaded"). So it seems that the whole networking is broken in Windows right now.

This used to work with the latest stable release of Win10, which I am now going to downgrade to.

[jackchammons]

I can reproduce on 14965

[saschagehlich]

I noticed that my network errors were caused by my Antivirus / Firewall "ESET NOD32". Uninstalling it fixed the download issues.

[LordMonoxide]

Probably related to #1377? See my comment at the bottom of the thread for details

[saschagehlich]

I was able to track this down to my Antivirus software (NOD32) which doew not seem to play well with the insider build.

…

On Dec 5, 2016 8:24 PM, "Corey Frenette" ***@***.***> wrote: Probably related to #1377 <#1377>? See my comment at the bottom of the thread for details — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1413 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAHThDWZ31GCK_hdWu1TXdUmMU7AM-yJks5rFGTzgaJpZM4K7sb4> .

[LordMonoxide]

I don't use an antivirus, but I'm guessing #610 is my issue

[scooley]

Closing as a duplicate of another issue (which has been fixed). #610