puts "Content-Type: text/html"
puts
puts "... rest of output ..."
That may or may not be the problem. You'll need to be more specific
about what you see.
You may also need to set the execute bit on script.rb (chmod +x
script.rb - but if you're on a hosted service you may be able to do this
over FTP/SFTP with a 'site chmod' command. Consult your service
provider)
Are you sure the hosting provider actually allows telnet connections?
You probably shouldn't use telnet anyway -- try SSH instead. My first
rule when looking at shared hosting providers is that I won't use one
that doesn't allow me encrypted remote access. Since telnet isn't
encrypted, a man-in-the-middle attack (among other means) can be used to
intercept your username and password when you try to log in via telnet.
···
On Wed, Dec 03, 2008 at 04:04:28AM +0900, ZippySwish wrote:
Well, telnet can't get a connection for some reason, but what I mean
by "nothing's happening" is I put
Dude, totally missing the point -- the idea is to use your local telnet
client to test the connection to *port 80* and directly examine the
http server's response.
Nothing to do with logins, passwords, etc.
···
On Thu, Dec 4, 2008 at 9:24 AM, Chad Perrin <perrin@apotheon.com> wrote:
Are you sure the hosting provider actually allows telnet connections?
You probably shouldn't use telnet anyway -- try SSH instead.
Alternatively, the Firefox WebDeveloper plugin allows you to view the http
response.
~m
···
On Thu, Dec 4, 2008 at 12:54 PM, Hassan Schroeder < hassan.schroeder@gmail.com> wrote:
On Thu, Dec 4, 2008 at 9:24 AM, Chad Perrin <perrin@apotheon.com> wrote:
> Are you sure the hosting provider actually allows telnet connections?
>
> You probably shouldn't use telnet anyway -- try SSH instead.
Dude, totally missing the point -- the idea is to use your local telnet
client to test the connection to *port 80* and directly examine the
http server's response.
You're right -- I missed that point, probably because I tend to use other
tools for the same purpose.
···
On Fri, Dec 05, 2008 at 02:54:55AM +0900, Hassan Schroeder wrote:
On Thu, Dec 4, 2008 at 9:24 AM, Chad Perrin <perrin@apotheon.com> wrote:
> Are you sure the hosting provider actually allows telnet connections?
>
> You probably shouldn't use telnet anyway -- try SSH instead.
Dude, totally missing the point -- the idea is to use your local telnet
client to test the connection to *port 80* and directly examine the
http server's response.
Nothing to do with logins, passwords, etc.
--
Chad Perrin [ content licensed PDL: http://pdl.apotheon.org ]
awj @reddit: "The terms never and always are never always true."