If you can't get a response, it either crashed, or is being updated.
Now that I it seems to work again, I see that you do nothing to simplify caching.
In response to this:
Accept:application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3
Accept-Encoding:gzip,deflate,sdch
Accept-Language:en-US,en;q=0.8,sv;q=0.6
Connection:keep-alive
Host:syerjchep.org
Referer:http://syerjchep.org/requestlog.html
User-Agent:Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.205 Safari/534.16
You send me this:
Connection:close
Content-Length:287
Content-Type:text/html; charset=UTF-8
Some whitespace got cut off when copy-pasting.
Still though, you don't send anything related to caching, and you don't compress the output.
That, for example, is why you should let someone else do the heavy http lifting for you, instead of trying to reinvent the wheel.