>> However, when I try to use a web browser (Firefox) to connect
>> to http://192.168.1.65:8023 , I RARELY get the http header (GET request,
>> etc.). Most of the time, the browser doesn't seem to send anything. But,
>> if I send data back to it, then disconnect, it DOES show up on the
>> browser.
>
> What does your reply look like to the browser?  If you don't send
> content-type and content-length, it will wait until the connection is
> dropped to display the page.
>

Thanks for the comments! I'm not sure what I did, but got it working.
Every now and then the request from the browser either doesn't show up, or
gets cut off in the middle. I'm dumping received data out to a terminal so
I can watch what's going on. I think I've just got something wrong with
the radio module, perhaps with the SPI timing. I'm trying to get a timing
diagram out of the manufacturer as to what the SPI is supposed to look
like.

Thus far I am not including content length and, as you point out, the page
is not rendered by the browser until the connection is dropped. I'll try
adding content length tomorrow. The page I'm sending is plain old html. I
assume the length is a decimal count of bytes after the end of the header
(after the \r\n\r\n).

Thanks!

Harold


-- 
FCC Rules Updated Daily at http://www.hallikainen.com - Advertising
opportunities available!
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist