Hello Nihat,
The server you've connected to has sent you the messsage "500 Internal Server Error". It means that some sort of any error has occurred on that server. Then, it disconnected without sending back any sort of response document.
Its hard to say what is causing the error, since it is occurring on the server, and it does not explain the problem, it just disconnects. Its possible that you are sending it the wrong data, or data in the wrong format, and that is causing an error. Its
also possible that there's something wrong with the server.
As Brad said, I'd double-check that you're doing everything correctly -- and if so, I'd contact the folks who run this server and ask them if something is wrong.
Its important to understand that every API is different. Since nobody on this mailing list is familiar with the exact API you're calling, there's no way we can tell you what you are doing wrong -- at least, not without more information. You'll want to
look in the documentation for the API and/or talk to the people who run it to get more details. If you have an example that works in a tool like Postman, SoapUI or curl, then we could compare that to what you've done in HTTPAPI to tell you what must be changed.
--
Scott Klement
sk@xxxxxxxxxxxxxxxx
On 12/9/2020 1:05 PM, Nihat Ezer wrote:
Greetings,
SetError() Ö13: HTTP/1.1 500 Internal Server Error
recvresp(): end with 500
recvdoc parms: identity 0
header_load_cookies() entered
recvdoc(): entered
SetError() Ö0:
recvdoc(): No content-length: receiving until disconnect
SetError() Ö44: CommTCP_read: Socket has been shut down.
SetError() Ö13: HTTP/1.1 500 Internal Server Error
http_close(): entered
************End of Data********************
Receive the error above during the http_url_post_raw() and have come the following which did not help much, http://www.scottklement.com/archives/ftpapi/201806/msg00005.html