HTTP is not based on the telnet protocol. There's actually a few things wrong with using telnet as a basis for "testing" a HTTP server. First, telnet sends some extra bytes immediately after establishing a TCP connection to setup the session parameters. Second, HTTP does not echo data sent by the remote peer. Third, good IPS devices can drop connections to the HTTP port when that initial session data is sent, or when protocol violations are encountered.
Using the telnet client to test a HTTP server is hack-ish at best. The client will display a blank-screen when the TCP session is established, and will only display what the server sends back. If you're clever, you might be able to retrieve a page on many servers... but I would consider it bad-practice. Read up on the HTTP protocol on how to format a GET
request.
A basic http request is done as follows:
GET / HTTP/1.0
Note the extra line after the request. A complete request ends with a blank newline.
Whoever voted down this question, you are welcome to explain in the comments what you found wrong about it. – None – 2012-11-01T16:37:49.503