AFAIK, unless there is content-length header or chunked encoding, the connection is "close" and cannot be keep-alive since the browser understands the end of data when the socket is closed.
Best Regards, SZ ----- Original Message ----- From: "S.Korotky" <[EMAIL PROTECTED]> To: "ICS support mailing" <twsocket@elists.org> Sent: Saturday, March 10, 2007 11:15 AM Subject: [twsocket] How to handle a Keep-Alive connection withoutContent-Length in a header? > Hello All! > > I need an advice on how to handle keep-alive and possibly pipe-lined > connections. > Am I right that the only direction on when a requested document is filly > received is > the value of the Content-Length header? If so, what to do if the > Content-Length is > missing? I need to fire OnHeader/DocBegin and OnHeader/DocEnd events > properly, > and yet sometimes a server (even IIS) returns a HTTP-header without a > content-length > value. The connection should be kept alive, but all subsequent data flow > becomes > screwed up in the manner that documents are hardly to extract in a > reliable way. > Should I parse all incoming data for searching for next headers? > Or Am I missing something? > > Thanks in advance. > > Best wishes, > Stanislav Korotky. > > -- > To unsubscribe or change your settings for TWSocket mailing list > please goto http://www.elists.org/mailman/listinfo/twsocket > Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
