Quick question

Post #4,538 by tjsinclair 8/10/01 3:27:19 PM Reply	Quick question I'm telling my students about well known ports in TCP and UDP this week. I'd like to demo how to telnet to port 80 on a Web server and get it to spit out the server software and OS but I don't remember what I have to type in to get the header info. If I just use GET, it returns the HTML for a 400 error page and I can also request a specific document but how do I get the server header info? This probably sounds really trivial and stupid but I've looked through Google and Slashdot already with no luck.
Post #4,560 by Another Scott 8/10/01 7:11:05 PM Reply	Try this. According to [link\|http://www.google.com/search?q=cache:ikjN3K6Euy4:everythinglinux.org/webserver/webserver_content.html+web+server+software+http+telnet+port+80&hl=en\|This] article from everythinglinux.org (via Google's cache) you want to: To test whether or not your server is up, you can use a browser, or even simpler, telnet to port 80 (or other, as above) of your machine: $ telnet localhost 80 Trying 127.0.0.1... Escape character is '^]'. GET / HTTP 1.0 HTTP/1.0 200 OK Date: Sun, 16 Jul 2000 19:09:37 GMT Server: Apache/1.1.3 Content-type: text/html Note that YOU actually have to type the line "GET / HTTP 1.0" followed by two carriage returns. What you'll get in return is the response header "HTTP/1.0 200 OK" which includes the response code "200" - meaning that your server responded as it should. You'll also notice the line "Server: Apache/1.1.3" or similar, depending on your version of Apache. This serves to identify the software you're using to serve your material. All servers do this, and is how Netcraft performs their Web server software survey. Haven't tried it myself. (And it was surprisingly difficult to find!) HTH. Cheers, Scott.
Post #4,597 by tjsinclair 8/11/01 12:24:03 AM Reply	Thank you very much! Not only for digging this up, but for verifying the difficulty of my search. I knew that I had seen it somewhere but it was a long time ago.
Post #4,605 by static 8/11/01 2:58:14 AM Reply	scratches head My first instinct would have been to get the HTTP RFC and just try things with the commands browsers are supposed to be able to send. Which reminds me: if you do a GET / HTTP/1.1 then the server will expect a Host: line as well. Otherwise it will probably give an error. Host: is fortunately optional in HTTP/1.0 Wade. "All around me are nothing but fakes Come with me on the biggest fake of all!"
Post #4,656 by tjsinclair 8/11/01 6:11:00 PM Reply	Aw, you always want to RTFM.....<grin>
Post #4,807 by static 8/12/01 10:59:52 PM Reply	Well, it worked, didn't it? :-) "All around me are nothing but fakes Come with me on the biggest fake of all!"
Post #4,685 by ben_tilly 8/11/01 10:16:13 PM Reply	Strangely enough... My natural response would be, "I know that Perl's LWP module can send HTTP requests, what do they print?" It took me just a couple of minutes to track down the request method in LWP/Protocol/http.pm and it would have been very easy to have made a custom copy, change the 3 syswrites to also echo debugging output, then send a request somewhere... Cheers, Ben
Post #5,421 by cforde 8/16/01 11:02:31 AM Reply	even stranger I would have reached for [link\|http://208.223.9.21/jfd/java/tcp/tcp.html\|TCPReflector]. Have fun, Carl Forde

Welcome to IWETHEY!