Can't get response to http request

Question

linux

The essence of the problem:

wget -T 5 --no-proxy -t 1 www.oyy.ru/
I can't get a response to an http request from the server.

--2013-03-26 00:44:42-- www.oyy.ru/ www.oyy.ru is recognized … 81.176.239.210 Connecting to www.oyy.ru|81.176.239.210| :80... connection established. HTTP request sent, awaiting response... Read error (Connection timed out) in headers. Completion.

Throws out on timeout. Also when using other programs curl, lynx.

At the moment, this problem is only with this site. (I noticed similar problems with other sites before, but after cleaning iptables it is not visible.) A day ago there was no problem. The administration says that it does not block. Before the problem, he tormented his car a little. The site is accessible from the home computer. Including through wget. The bottom line is that both the server and the home computer are behind nat and have one external ip. iptables is empty.

It is interesting that codes other than 200 are obtained successfully.
# wget -T 5 --no-proxy -t 1 www.oyy.ru/index.php --2013-03-26 00:51:23-- www.oyy.ru/index.php www.oyy is recognized . ru … 81.176.239.210 Connecting to www.oyy.ru|81.176.239.210|:80... connection established. HTTP request sent, waiting for response... 404 Not Found 2013-03-26 00:51:23 ERROR 404: Not Found.

Question: On what side is the problem on the server, or is the site itself blocking. If the site is how it can determine the server if the ip on the two machines is the same.

Thank you.

Answer 1

Do other sites have this problem? (google there, yandex, others)
The last time I saw such strange symptoms, the problem was in the MTU on the target machine, (404, etc., smaller in size).
After reducing this parameter (or rather TCP MSS on the default route), everything worked.

Answer 2

Try to make an entry in /etc/hosts for this site, don't forget to run sudo /etc/init.d/networking restart afterwards

Answer 3

To better control the process, send a request using telnet.
If everything returns successfully via telnet, then raise your server, which will collect HTTP headers and contact your web server from wget (which will return a list of HTTP headers).
Then send the same headers via telnet as wget sends. The problem should come up. Chemistry with headlines and try to understand what exactly is wrong.
If the site successfully captures such headers, then wait for the following responses.

Answer 4

Perhaps there is a blocking by user-agent. Try adding --user-agent="Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)" argument