Empty response.

[Zensey]

Describe the bug
When connected to certain nodes all TCP responses are empty.

To Reproduce
Steps to reproduce the behavior:

1. Connect
2. Run command:

curl.exe -v http://hello-world:8080/index123
*   Trying hello-world:8080...
* Connected to hello-world (hello-world) port 8080
> GET /index123 HTTP/1.1
> Host: hello-world:8080
> User-Agent: curl/8.4.0
> Accept: */*
>
* Empty reply from server
* Closing connection
curl: (52) Empty reply from server

Nodes that are known to have an empty TCP responses:
windows:
0x07ca2cd1079490a005e551da5d2f8a2dc516222f
0x0733df3b8cb3ed5f13ba860d19c686e88437189f
darwin:
0x1a52807858619c4acb2a075b659a86dbe459bc98
0x0f7689807782b66d0569783ea6e56883b02240b5

[Zensey]

Logs from my web server show that it gets a correct request and reply is also done successfully,
so I suspect some firewall rule or app is what interferes.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[Zensey]

Internal spreadsheet with node runners feedback on this issue
https://docs.google.com/spreadsheets/d/19HfNETFTQo2EBYDhFMsr2J2KbCpLhb5SeP29Ix1wVk4/edit?gid=0#gid=0