Further investigation, which you can do yourself, reveals that your server *is* actually sending a 500 response.
Try this:
- Use Firefox
- Enable the LiveHTTPheaders extension
- Visit the site
You'll see that the first response is indeed a 500 Internal Server error response.
So, wget is legitimately saying what's really going on. Human browser viewing is apparently ignoring that in favor of the rest of the data that follows it.
As the host, you'll need to fix whatever's triggering that from your server.
Code:
http://www.futurehouse.gr/
GET / HTTP/1.1
Host: www.futurehouse.gr
User-Agent: Mozilla/5.0 ... Gecko/20100101 Firefox/6.0.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip, deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
DNT: 1
Connection: keep-alive
Cache-Control: max-age=0
HTTP/1.1 500 Internal Server Error
Date: Tue, 06 Sep 2011 18:19:26 GMT
Server: Apache
X-Powered-By: PHP/5.2.17
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Content-Encoding: gzip
Vary: Accept-Encoding
Connection: close
Transfer-Encoding: chunked
Content-Type: text/html; charset=utf-8
Bookmarks