[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    Re: [BusyBox] nc: Problems reaching some servers
From:       Calle Be <callebe.geo () yahoo ! com>
Date:       2003-02-20 17:11:14
[Download RAW message or body]

Oki, thanx!

So, can the <CR><LF> problem be solved? How can I send a <CR> instead of a
<LF>? And the other reply was that busybox nc only supports udp. Is there a way
around that?

/Calle Be

--- Charles Steinkuehler <charles@steinkuehler.net> wrote:
> Calle Be wrote:
> > Jucklo!
> > 
> > I'm using busybox (what version? I dunno. where?) and am currently trying
> to
> > netcat into komfram.trafikkontoret.goteborg.se. Now, this does not seem to
> > work.
> > 
> > When I connect to other servers, I get a new line and type something like:
> > 
> >   GET /some_dir/some_file.html HTTP/1.0
> > 
> > nc then answers with the source of that file. However, when I type:
> > 
> >   nc komfram.trafikkontoret.goteborg.se 80
> >   GET /some_dir/some_file.html HTTP/1.0
> > 
> > nothing happens. I can write all and anything I want, but nothing happens.
> What
> > could possilby be wrong? I have tried the samething with a windows version
> of
> > netcat (Netcat 1.10 for NT) and that works just fine. I have also tried
> with
> > tkweb4.trafik.... and the ip. No result.
> 
> You probably have an improperly formatted http request.  You need the 
> proper terminating string: "<CR><LF><CR><LF>" or some servers will not 
> recognize your request.  While some servers tolerate <LF> and/or <CR> 
> only end-of-lines, the RFC's say to use <CR><LF>
> 
> There could also be other issues (ie server responds only if you send 
> appropriate data in various headers, and ignores you otherwise), but I 
> suspect you're probably having a <CR><LF> problem.
> 
> -- 
> Charles Steinkuehler
> charles@steinkuehler.net
> 
> 


__________________________________________________
Do you Yahoo!?
Yahoo! Tax Center - forms, calculators, tips, more
http://taxes.yahoo.com/

[prev in list] [next in list] [prev in thread] [next in thread]