C # the following error occurs when post data: system. net. webexception: Remote Server Return Error: (417) Expectation failed solution

. Net (client) Call PHP (server) Error 417

Problem description:
Server environment:
Linux + Apache (Lighttpd) + PhP5

Client environment:
Windows XP + IIS +. net


The following error occurs during the call:
System. net. webexception: Error returned by the remote server: (417) Expectation failed. In system. net. httpwebrequest. getresponse () in org. phprpc. phprpc_client.post (string requeststring) at Org. phprpc. phprpc_client.invoke (string function, object [] ARGs, Boolean byref, byte encryptmode)

Detected error:
If the service is written on a Windows machine, the error will disappear.


After guidance from the cool "prodigy:
Write. net Program Start-up Code Or in a file such as app. config.
Just add this sentence.
Servicepointmanager. expect100continue = false;


Good results, problem solving



To sum up the reasons:
The httpwebrequest control has a transparent process. It first queries the service provider for the existence of a URL without sending post content. If the server confirms that the URL is accessible, it sends a post, early Apache thought this was an error, but IIS was able to respond correctly (prodigy) . Net (client) Call PHP (server) Error 417

Problem description:
Server environment:
Linux + Apache (Lighttpd) + PhP5

Client environment:
Windows XP + IIS +. net


The following error occurs during the call:
System. net. webexception: Error returned by the remote server: (417) Expectation failed. In system. net. httpwebrequest. getresponse () in org. phprpc. phprpc_client.post (string requeststring) at Org. phprpc. phprpc_client.invoke (string function, object [] ARGs, Boolean byref, byte encryptmode)

Detected error:
If the service is written on a Windows machine, the error will disappear.


After guidance from the cool "prodigy:
The. NET program is written in the initial code, or in a file such as the configuration file app. config.
Just add this sentence.
Servicepointmanager. expect100continue = false;


Good results, problem solving



To sum up the reasons:
The httpwebrequest control has a transparent process. It first queries the service provider for the existence of a URL without sending post content. If the server confirms that the URL is accessible, it sends a post, early Apache thought this was an error, but IIS was able to respond correctly (prodigy)