mini-server question

Henrik,

In order to due some testing of the socket library I am using to build the
library and mini-server on, I short circuited the default response header
output in HTTPServe.c, by adding the following line to the begining of
MakeReplyPipe()

 return HT_OK;  // JTD - temporarily short circut response header

This of course, causes the library to pass the headerless stream right
through to the socket (and to the connected browser). For test purposes
I am using an HTML document containing some 50 gif icons, ranging in size
from 174 bytes to 1.5K.

I was very suprised to find that, even without any headers, Netscape was able
guess the file type and correctly display the html page and most of the icons
properly. (Only 3 small icons 174-207 bytes don't display properly. I suspect
this is due to the fact that NetScape probably expects a minimum size for
header+content and the small icon's content falls below this size.)

Anyway, this has been very benificial, as if has permited me to test and debug
the socket library (which originally had problems when multiple sockets and
heavy i/o took place). After correcting these difficulties I have sucessfully
had as many as 19 sockets handling i/o simultaniously, with very good
throughput and no detectable memory leaks.
I am very impressed!

Now a question. Could you briefly outline the calls necessary to properly build
the correct reponse headers, based on mime type?

I have read the message to Markku Savela, concerning making mini-server into a
proxy server but, I don't need to do any translation of the stream, I just want
to add headers and set their correct content length, etc. Do I still have to add
an 'ImageObject' converter?

In short I just want to make mini-server into a full-blown httpd, but who
doesn't. (: Any advice would be appreciated.

Thanks for you time. sinc, -j

freesoft@ccia.com (Jeff Dripps)

Received on Friday, 1 March 1996 11:30:15 UTC