HttpWebRequest introduces significant delay when the Expect100Continue header is disabled

Question

When disabling the Expect100Continue header for the HttpWebRequests coming out of my WCF host client, adding the following section to the settings section in the configuration file:

ServicePointManager.Expect100Continue=false 

I noticed that the client waits about 150 milliseconds between sending the HTTP POST request and the next TCP packet that contains the actual payload.

Any question why this might happen? This is unexpected because when I turn off this header, I expect the payload to be sent immediately after the initial request without latency.

Answer 1

, , .NET Naggle TCP. , , :

ServicePointManager.UseNaggleAlgorithm=false.                       

150 .