Ladies and gentlemen, meet a problem, use idhttp d7, send a post request webservice interface, using the online simulation interface is no problem, but access to the company's services out of the question: HTTP/1.1 500 Internal Server Error? A mystery!!!!!!

http://192.168.5.10//DeviceInterface/DeviceInterface.asmx/DeviceInformation_Coating
DeviceInfo_Coating={" MachineID ":" ABC - 001 ", "RunTime" : "3500", "DateTime" : "the 2020-10-20 21:50:00", "Status" : "0" and "DetailsInfo" : [{" ItemCode ":" 909 ", "Result" : "OK", "Value" : ""," Remark ":" normal "}]}

* * * * * * * * * * * * * * * * * * * * * * * * * * *
The log @ 2020-10-26 08:13:16 & gt;>
To send data: Verify_BarcodeInfo_Coating={" OperatorID ":" 113671 ", "MO" : "000082165563 _1", "Barcode" : "2102312 fgvlul8001524", "MachineID" : "ABC - 001", "DateTime" : "the 2019-11-30 14:13:02"}
Abnormal interface: HTTP/1.1 500 Internal Server Error

* * * * * * * * * * * * * * * * * * * * * * * * * * *

CodePudding user response:

You this is an internal server error, change the simple story is your webservice service when dealing with the abnormal,
Reason is that your service program of internal process may have a problem to receive data (including processing fault tolerance),

CodePudding user response:

reference 1st floor tanqth response:

this is an internal server error, you change the simple words, your webservice service when dealing with the abnormal,
Reason is that your service program may have a problem of internal process (including process receives the data of fault tolerance),

Ok, will send on my side of the parameters of the other party fault-tolerant processing, result in abnormal? I check in this direction!

CodePudding user response:

Brothers, my problem solved! , after the inspection service written by asp.net found each other, then calls the test page, found that only support local call, and then found that only the soap specification, at the same time adopt apipost call interface testing, complains! So the suspect does not support httpost, so ask for check web. Config, found that yao has support httpost configuration!

So the requirement in the web. Config & lt; System. Web> Join the following configuration sections of content






After restart the service! Very exciting thing happened!

CodePudding user response:

reference flywolf brother reply: 3/f

, brethren, my problem solved! , after the inspection service written by asp.net found each other, then calls the test page, found that only support local call, and then found that only the soap specification, at the same time adopt apipost call interface testing, complains! So the suspect does not support httpost, so ask for check web. Config, found that yao has support httpost configuration!

So the requirement in the web. Config & lt; System. Web> Join the following configuration sections of content






After restart the service! Very exciting thing happened!