On Saturday, October 12, 2013 2:21 PM [GMT+1=CET], Laurent Breysse wrote: > Resolved: The issue came from AVAST antivirus, which is altering the > connection content in some way.
I reproduced that as well with AVAST **BUT** that doesn't seem to be the culprit here. When I run the Client from a different physical Host the timeout happens again (without any AV). HttpServer1PostDocument triggers however HttpServer1PostedData does not. When the connection is closed the posted data is received however treated as a new request and a 501 response is sent to client. We have a timing bug obviously since both client and server on localhost does work except when AVAST is installed. -- Arno -- 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
