It's very possible for Content-Length to be missing. For example, the client program could be sending a number of files each of which will go thru gzip (or other compression) before being sent. Unless the client program chooses to zip (and base-64-encode?) everything to be sent before starting to send, it won't be able to provide the Content-Length.
Not reading it all is Bad Form. At 09:46 AM 3/29/2006, Peter Ritchie wrote (in part) >The content-length value is application layer data. That should be >separated from the transport layer (i.e. the layer that sends/receives the >data over TCP). > >You could stream the data into the application data for processing before >all the data has been received; but, you should have transport layer logic >to receive all the data, regardless of its content. Many browsers don't >play nice with servers that disconnect their socket before they finish >sending. [snip] J. Merrill / Analytical Software Corp =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
