digg.com, your webserver just sucks

Thursday, July 31. 2008

digg.com, your webserver just sucks

Hey, digg.com, yes, you! Your webserver just sucks. Have you ever found the time to read the relevant HTTP-related RFCs, like 1945 or 2616? I don't think so, otherwise you'd know that the User-Agent request header is not mandatory. Recommended, but definitely not mandatory. So why in hell's name does your webserver simply close the connection when sending an HTTP request without User-Agent header, and why does it keep the connection open without any response when I send a request without User-Agent header but with a Connection: keep-alive header? I've never seen an HTTP server implementation that is broken in a more braindead way. If you don't like clients w/o User-Agent header, why couldn't you at least reply with a nice "HTTP/1.1 5xx Fuck You"? Absolutely ridiculous.

Posted by Andreas Krennmair at 20:40 | Comments (0) | Trackbacks (0)

Defined tags for this entry: digg, http, rant

Related entries by tags:

Trackbacks

Trackback specific URI for this entry

No Trackbacks

Comments

Display comments as (Linear | Threaded)

No comments

Add Comment

Name
Email
Homepage
In reply to
Comment	Enclosing asterisks marks text as bold (word), underscore are made via _word_. Standard emoticons like :-) and ;-) are converted to images. You can use [geshi lang=lang_name [,ln={y\|n}]][/geshi] tags to embed source code snippets. To prevent automated Bots from commentspamming, please enter the string you see in the image below in the appropriate input box. Your comment will only be submitted if the strings match. Please ensure that your browser supports and accepts cookies, or your comment cannot be verified correctly. Enter the string from the spam-prevention image above:
	Remember Information? Subscribe to this entry