Take a look at Expect100Continue!
When this property is set to true, client requests that use the POST method expect to receive a 100-Continue response from the server to indicate that the client should send the data to be posted. This mechanism allows clients to avoid sending large amounts of data over the network when the server, based on the request headers, intends to reject the request. For example, assume the System.Net.Sockets.ServicePointManager.Expect100Continue property is false. When the request is sent to the server, it includes the data. If after reading the request headers, the server requires authentication and must send a 401 response, the client must resend the data with proper authentication headers. If this property is true, the request headers are sent to the server. If the server has not rejected the request, it sends a 100-Continue response signaling that the data can be transmitted. If, like in the previous example, the server requires authentication, it sends the 401 response and the client has not unnecessarily transmitted the data.
Changing the value of this property does not affect existing service points. Only new service points created after the change are affected.
The Expect 100-Continue behavior is fully described in IETF RFC 2616 Section 10.1.1
See: ServicePointManager.Expect100Continue Property
With regard to the above the following backgrouder might be usefull to you:
Understanding System.Net Connection Management and ServicepointManager
When this property is set to true, client requests that use the POST method expect to receive a 100-Continue response from the server to indicate that the client should send the data to be posted. This mechanism allows clients to avoid sending large amounts of data over the network when the server, based on the request headers, intends to reject the request. For example, assume the System.Net.Sockets.ServicePointManager.Expect100Continue property is false. When the request is sent to the server, it includes the data. If after reading the request headers, the server requires authentication and must send a 401 response, the client must resend the data with proper authentication headers. If this property is true, the request headers are sent to the server. If the server has not rejected the request, it sends a 100-Continue response signaling that the data can be transmitted. If, like in the previous example, the server requires authentication, it sends the 401 response and the client has not unnecessarily transmitted the data.
Changing the value of this property does not affect existing service points. Only new service points created after the change are affected.
The Expect 100-Continue behavior is fully described in IETF RFC 2616 Section 10.1.1
See: ServicePointManager.Expect100Continue Property
With regard to the above the following backgrouder might be usefull to you:
Understanding System.Net Connection Management and ServicepointManager
Reacties