During a relocation an intermediary RequestDone events is fired. Is this really needed, and for what propose? If yes, then I think it should be fired with the correct response status code, not zero as now, so it can be clearly detected as not the final request done even. Also, an "httpRelocating" THttpState could be handy. This behavior is also inconsistent. If the client is configured to use HTTP 1.0, and no Keep-Alive header is send, this intermediary RequestDone event is not triggered.

Rui
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be

Reply via email to