Hi,
On Fri, 20 Dec 2002 10:38:20 +0530
"Manjunath H N" <manjunath@iwavesystems.com> wrote:
> > You'd be better off telnetting to port 80 and issuing an
> > apporpriate GET / HTTP/1.0 request.
>
> Telnetting to that port can be blocked on their firewall so this option
> cannot be used for all sites.
You misunderstand the power of "telnet". If you "telnet somehost" you make a TCP
connection to port 23 on host "somehost". If you "telnet somehost 80" you make a
TCP connection to port 80 on "somehost". This is not different to using a
browser. If "telnet" to port 80 is blocked by the firewall, then the webserver
cannot be accessed by anyone.
> Well Anyway I tried that, it says connection to host lost & how to issue
> GET/HTTP/1.0 request.
>
> Well the site can be accessed in other places. I checked with a few of my
> friends in other companies, but only my proxy is giving this error.
If you cannot telnet to port 80 on the web server
a) you are being denied access. The connection will either eventually time out
or die immediately (if they send a TCP reset).
b) the web server is not running (you'll get a "connection refused" message).
So, exactly what happens when you telnet to port 80?
Just in case you are not sure what to do (on a Unix host, you would):
telnet hostname 80
<get a connection message>
GET / HTTP/1.0
After the "GET" you have to hit Enter twice - the first one terminates the HTTP
request. The second terminates the (empty) list of HTTP headers.
Colin
-- Colin Campbell Unix Support/Postmaster/Hostmaster CITEC +61 7 3227 6334Received on Thu Dec 19 2002 - 22:25:16 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:12:10 MST