2 ms·
I'm afraid my system does not have yet support to http protocol This server does not apparently has any service listening on port 23 so unfortunately I can't t
by raverbashing 14y ago
I'm afraid my system does not have yet support to http protocol
This server does not apparently has any service listening on port 23 so unfortunately I can't telnet to it (I'm not sure what's this /jobs as well, is this a Gopher page? oh well...)
- laumars 14y agoPort 22 is SSH. Telneting to it wouldn't do much good aside telling you which sshd was listening. I'm also a little confused by what you mean when you said your system doesn't support "HTTP protocol", curl has been a staple for Unix and Linux for over a decade. Or are you trying to run curl from cmd.exe in windows?
- raverbashing 14y agoI meant port 23, sorry And maybe you're too young to understand the joke ;)
- laumars 14y agoPossibly. I know good jokes are ruined if they have to be explained, but would you mind on this occasion :)
- lloeki 14y agoSaving the explanation, try this: $ telnet towel.blinkenlights.nl
- laumars 14y agoI don't think there's a single nerd on the planet who hasn't already seen that.
- raverbashing 14y agoWell, here goes: Once upon a time (around 1995, first time I tried this 'internet' thing) the internet already existed. But this newfangled http protocol was not very popular (it existed since 1991) You see, Curl was created in 1997, Wget in 1996 The way to access systems was through telnet mostly. Some modern clients, like lynx, also supported Gopher http://en.wikipedia.org/wiki/Gopher_(protocol) http://en.wikipedia.org/wiki/Gopher_(protocol) (Yes, lynx got http support at a later time) So, their choice for a page readable from a terminal ends up being kind of an Anachronism =)
- laumars 14y agoOh, I know all that (I was building websites in the mid 90s, so I'm old enough to remember a life before the WWW). I assumed you were referencing an old meme or a famous quote from some notable UNIX greybeard. I hadn't realised you were just joking about being old (that wasn't clear from your original comment). Sorry mate, I just misunderstood the context of your joke. (my epic lack of sleep probably didn't help)
- raverbashing 14y agoAh it happens, don't worry =)
- lloeki 14y agoI hoped this would work: $ telnet cueup.com 80 GET /jobs HTTP/1.1 User-Agent: curl/7.24.0 (x86_64-apple-darwin12.0) libcurl/7.24.0 OpenSSL/0.9.8r zlib/1.2.5 Host: cueup.com Accept: */* <blank line> but it redirects to Location: https://www.cueup.com/jobs https://www.cueup.com/jobs, so this is necessary: $ openssl s_client -connect www.cueup.com:443 GET /jobs HTTP/1.1 User-Agent: curl/7.24.0 (x86_64-apple-darwin12.0) libcurl/7.24.0 OpenSSL/0.9.8r zlib/1.2.5 Host: www.cueup.com Accept: */* <blank line> And there you go (^D to stop). Unfortunately things get munged up since it's using Transfer-Encoding: chunked, so there's the chunk size and blank line in between each content line. Bonus points for cueup.com if they update the thing to not chunk it if User-Agent: telnet (I did test this and it doesn't work)