You can test that on the client side by simply changing the 'Host' line above replace with the site you're trying to reach: GET / HTTP/1.1 If that's the case, depending on server configuration (the site you're trying to hit happens to be configured as the default) you cannot reach the site by IP address without a little bit of work. One possible reason you are getting an empty reply is that you're trying to hit a website that is a name-based virtual host. You should see the response exactly as curl sees it. Once connected, paste the following (taken from your curl output): GET / HTTP/1.1 You can test this by simply using telnet instead of going through curl: telnet 111.222.159.30 80 Likely you are getting a reply that does not contain any data. I believe you are confusing an 'empty response' with 'no response'. You likely will need to troubleshoot this from the server side, not the client side. Note, I'm a bit green at this level of networking, so feel free to provide some general orientation material. It was able to successfully 'connect', so doesn't that involve some bidirectional communication? If so, then why does the response not come also? Note, I've verified my service is up and returning responses. No problem, that's precisely what I'm trying to figure out.īut what more specific info can I derive from cURL here? So, I understand that an empty response means that curl didn't get any response from the server. I'm not looking for help that would be dependent upon my environment, I just want to know how to collect information about exactly what part of the communication is failing, port numbers, etc. I want to know how to proceed in troubleshooting why a curl request to a webserver doesn't work.

Xsplit download error empty response