Thanks, I have added the chunker information to the POST exploration plugin where it is generating the snoop reply. That plugin also generates a Cookie that tells the URLs that have been visited. The new version is updated on the web page. The thing that confuses me is on the page called Submit, when I attempt to post a large file. A small text file uploads ok, both the file name and the file contents appear to go just fine. A larger file, such as a small document file from BlackBox, appears to be truncated. There is a discrepancy between the number of bytes available and the Content-Length. So I am reading and puzzling here. For the project to go, I need to be able to upload some .gif or .jpg images that may get large. ... In planning for the future, I don't notice anything that I recognize as "Riders" in the AosIO package. It appears that I have to read character at a time and handle them as they arrive. The buffers that are hidden down with the Receiver are not available (naturally). I can encapsulate this and do as is my will, but I wonder if there is a library component that does it already. I will soon get into actual content production, and I comprehend the SSMP approach pretty well. As soon as I can have students upload files, I think that I can do everything I need. Is the Session Management/Dynamic Web project at the point that it has stable documentation or interface? -- Aubrey | In your code, you open a ChunkedOutStream with the line | | NEW(chunker, w, out, request, reply); | | The creation of the chunker automatically fills in the transfer encoding in the reply header. | But you missed to write the reply header at all. So to correct this problem, add | | WebHTTP.SendReplyHeader(reply, out); | | before using the chunked stream the first time. | | FYI: Some current projects with the Web-Server: | - IMAP - Webaccess (almost finished, code upon request) | - Session Management/Dynamic Web (XHTML) Pages (more flexible than SSMP) | - https | - Teletext Web-Service | |