Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am sending requests to a specific server on a cloud:

wget --header="Host:" http://x.x.x.x:80/
curl -i -H"Host:" http://x.x.x.x:80/

And it returns exactly as expected (a simple static file). However, when I try and access it in a browser, the request times out. I can't imagine it would be a user agent header issue, but then again, I don't really know what else it would be.

It isn't going to a load balancer or anything, should be going directly to the site. Any ideas on why this might be happening? I have my hosts file set to go to that specific IP address.


share|improve this question
Most likely, the browser is ignoring the hosts file and is not connecting to the IP address you are expecting it to. – David Schwartz Jul 11 '12 at 16:08
what does curl -i return? – vartec Jul 11 '12 at 16:21
Is the browser configured to use a proxy? – Aaron Copley Jul 11 '12 at 16:35

You need to look at the server to find out.

Can you see a request coming in to the webserver? (is there a tcp socket opened?)

What does the web server software log about the connection? Can you make it more verbose if it's not saying enough.

Failing that, tell us more about your webserver and its config.

share|improve this answer

Thanks everyone. It turns out there was an setting overriding the request, sending it to a new port that wasn't opened by the firewall...

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.