This is what I got from: telnet mail.poughkeepsieschools.org 80 Trying 64.72.66.117... Connected to mail.poughkeepsieschools.org (64.72.66.117). Escape character is '^]'. get index.php <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>400 Bad Request</title> </head><body> <h1>Bad Request</h1> <p>Your browser sent a request that this server could not understand.<br /> </p> </body></html> Connection closed by foreign host.
The server is accessed with https://... I'm not sure if I can use any of the above information.
Evan
<snip>
did you ever tried to do a manual telnet to school web server's port 80 ? # telnet school.server.com 80
If your Linux terminal throws back a error immediately you will know what is the problem. Otherwise, this should stay for some time, then just type: get index.html
and see if get any response from the server
regards
Yogesh
Evan Panagiotopoulos wrote:
This is what I got from: telnet mail.poughkeepsieschools.org 80 Trying 64.72.66.117... Connected to mail.poughkeepsieschools.org (64.72.66.117). Escape character is '^]'. get index.php
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head> <title>400 Bad Request</title> </head><body> <h1>Bad Request</h1> <p>Your browser sent a request that this server could not understand.<br /> </p> </body></html> Connection closed by foreign host.
The server is accessed with https://... I'm not sure if I can use any of the above information.
Evan
If you need to do it as an encrypted session (normally a 'https://...' address in a browser), try this:
openssl s_client -connect mail.poughkeepsieschools.org:443
Then you should get a bunch of stuff on the screen. After it stops, you should be able to treat it like a normal telnet session. I've always found supplying a little bit more information than just 'get index.php' is more helpful. I'd type this (replacing the <cr> with an enter -- HTTP requires two cr/lf's to signify the end of the header). Note the spaces around the first '/' in the first line, but no spaces around the second '/':
GET / HTTP/1.1 Host: mail.poughkeepsieschools.org <cr>
The output that follows should be a webpage. You can replace the first '/' in the first line with any relative path (so, for example, an address like http://mail.poughkeepsieschools.org/long/path/name/file.html would become "GET /long/path/name/file.html HTTP/1.1")
Hope this helps. Justin W
Evan Panagiotopoulos wrote:
This is what I got from: telnet mail.poughkeepsieschools.org 80
Looks like echo 1 > /proc/sys/net/ipv4/tcp_window_scaling (as root) will enable you to get there. This implies that there is a broken router between you and the site, which doesn't fully understand TCP/IP.
Note: setting this permanently can be done by adding the line net.ipv4.tcp_window_scaling=0 to /etc/sysctl.conf. This will limit the maximum speed of your TCP/IP connections.
Hope this helps,
James.
On Sun, 2007-02-25 at 15:22 -0500, Evan Panagiotopoulos wrote:
This is what I got from: telnet mail.poughkeepsieschools.org 80 Trying 64.72.66.117... Connected to mail.poughkeepsieschools.org (64.72.66.117). Escape character is '^]'. get index.php
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head> <title>400 Bad Request</title> </head><body> <h1>Bad Request</h1> <p>Your browser sent a request that this server could not understand.<br /> </p> </body></html> Connection closed by foreign host.
If you'd tried "GET" instead of "get" you might have got something else instead of a 400 error:
[tim@gonzales ~]$ telnet mail.poughkeepsieschools.org 80 Trying 64.72.66.117... Connected to mail.poughkeepsieschools.org (64.72.66.117). Escape character is '^]'. GET / <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>Found</h1> <p>The document has moved <a href="https://mail.poughkeepsieschools.org/">here</a>.</p> </body></html> Connection closed by foreign host.
I got a 302 (okay, but...) response. In a nutshell, that give you a response that tells you to use the address they provide back (the one in the HTTP headers, and they've provided the same details in the HTML, as well), instead of the one that you tried to use.
The address that you're redirected to use worked for me.
-
Andy Green -
Evan Panagiotopoulos -
James Wilkinson -
Justin Willmert -
Tim