Forums Developers Sockets

I can get this Google Searcher to work, anyone got an idea of whats wrong?
alias search {
sockclose google
set %search $replace($1-,$chr(32),+)
sockopen google www.google.com 80
}
on *:sockopen:google:{
if ($sockerr > 0) { return }
sockwrite -n google GET /search?q= $+ %search $+ &ie=UTF-8&oe=UTF-8&hl=en&meta=)
sockwrite -n google HOST www.google.com $+ $crlf $+ $crlf
}
on *:sockread:google:{
sockread %result
echo -a $chr(32) $htmlfree(%result)
}
alias htmlfree {
var %x, %i = $regsub($1-,/(^[^<]*>|<[^>]*>|<[^>]*$)/g,$null,%x), %x = $remove(%x,&nbsp;)
return %x
}

there's no need to post the same question on multiple boards, just simply post on 1 board and be patient for your answer(s)

as was pointed on on the other board...

sockwrite -n google GET /search?q= $+ %search $+ &ie=UTF-8&oe=UTF-8&hl=en&meta=)
sockwrite -n google HOST www.google.com $+ $crlf $+ $crlf

needs to be more like..

sockwrite -n google GET /search?q= $+ %search HTTP/1.0
sockwrite -n google HOST www.google.com
sockwrite -n google $crlf

It might be better if u had atleast some farmiliarity with the http protocol

Actually that's wrong, first you need a : after the word "host", and second you don't need the $crlf at the end of the third sockwrite..

sockclose google
set %search $replace($1-,$chr(32),+)
sockopen google www.google.com 80
/sockmark google /search?q= $+ %search $+ &ie=UTF-8&oe=UTF-8&hl=en&meta=)
}
on *:sockopen:google:{
if ($sockerr > 0) { return }
sockwrite -n google GET $sock($sockname).mark HTTP/1.1
sockwrite -n google ACCEPT: */*
sockwrite -n google HOST: www.google.com $+ $crlf $+ $crlf
}
on *:sockread:google:{
sockread %result
echo -a $chr(32) $htmlfree(%result)
}
alias htmlfree {
var %x, %i = $regsub($1-,/(^[^<]*>|<[^>]*>|<[^>]*$)/g,$null,%x), %x = $remove(%x,&nbsp;)
return %x
}

heh..knew i shouldn't have attepted that b4 i went to bed. Yes, hopst: has a colon, and the crlf is so there is a file return after the host is sent, symbolizing EOH (end of header). Anyways, if you don't put tsomething, it gives the "insifficient params" line >:\

Not for me, I have many HTTP scripts that do it, all of them use sockwrite -n $sockname, the -n sends a $crlf, don't need another $crlf. I like quibbling over details.

o watever.. >:\

However, even using -n sometimes doesnt work and you will still get the invalid parameters error. I had this happen commenly on sites using IIS 5+ where I had to actually send a seperate $crlf all by its lonesome. Unsure why IIS has this problem at times, maybe its the way its waits for the entire header sequence.