Back to home page

DOS ain't dead

Forum index page

Log in | Register

Back to the forum
Board view  Mix view

mTCP DOS - NC documentation issue (design bug)? (Announce)

posted by Arjay, 20.07.2010, 17:30
(edited by Arjay on 20.07.2010, 17:40)

> As always, it depends on the server.
Yup. Btw Slashdot is a good server to test with if you like Futurama :)

> A proper telnet newline is a carriage return and linefeed pair.
To be honest it's is ages since I read all the RFC's and indeed age since I coded web servers etc. Indeed in someways to be honest I am partly relearning technical (similar theme I was amused to read this recent blog posting by Trixter).

> Your post implies that only the LF is needed. If so, that's news to me
> - I thought that HTTP was expecting telnet newlines, not just plain LFs.
In a former life I spent more time with web stuff than I care to remember, however I could be wrong (often I am and happy to admit it ;), still I did do a few quick Google's to re-check facts. Anyway I guess we both need to do a bit of RTFM. Too many manuals to read+remember and just not enough time !!!

> (Just in case, I gave the user a command line option for sending the Enter
> key as a carriage return, or a CR/LF pair when using it interactively.
Neat :)

> I'm going to be doing wget shortly, so I'll crisp up the docs then.
Excellent. What about another cURL/libcURL, DOS port?

EDIT: wput?
I also noted that Daniel Stenberg has created 2 articles (biased obviously :) called:
curl vs wget
curl vs libcurl

 

Complete thread:

Back to the forum
Board view  Mix view
22780 Postings in 2123 Threads, 402 registered users (0 online)
DOS ain't dead | Admin contact
RSS Feed
powered by my little forum