Curl Server setup issue

I am using CurlSMBS to communicate with a client’s server. Who is preparing for a server update now, and we found we had to change some SSL settings to make them talk happily with each other again.

app → Server looks good:

10:57:03 curl debug (Text) : using HTTP/1.x
10:57:03 ServerPost 0%

    0/0
    0/0
    10:57:03 curl debug (Header sent) : POST /server HTTP/1.1
    Host: *2.*com
    Accept: /
    Transfer-Encoding: chunked
    Content-Type: application/x-www-form-urlencoded
    Expect: 100-continue
    10:57:03 curl debug (Text) : TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
    10:57:03 Server (title): OK
    10:57:03 URL https://2..com/*2/en/quickcheck
    10:57:03 curl debug (Header received) : HTTP/1.1 100 Continue
    10:57:03 curl debug (Header received)
    10:57:03 curl debug (Protocol data out) : 368
    |10:57:03|curl debug (Text) : upload completely sent off: 884 bytes|
    |—|—|

So protocol is agreed upon, all data sent.
But then this happens:

|10:57:03|curl debug (Header received) : HTTP/1.1 500 Internal Server Error|

And the response will come in as an error result from the server.
Any ideas what might be the cause?

Well, the application on the server doesn’t like what you sent.

Does it send more back like an error message?

Yes, but it does not give me much information:

10:56:25 ServerPost 0%
    0/0
    0/0
10:56:25 ServerPost 0%
    1210/0
    0/0
10:56:25 Server Response:<?xml version=1.0 encoding=UTF-8?><SOAP-ENV:Envelope xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/envelope/>SOAP-ENV:BodySOAP-ENV:FaultSOAP-ENV:ClientBad Request</SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>

With the old server setup, the same curl message gets a positive response.

If you do SOAP, you can’t use “Content-Type: application/x-www-form-urlencoded” as content type. You need something like “Content-Type: application/soap+xml;charset=UTF-8;action="urn:xxx"” ) with the right soap action there.

Oh, thank you! I will forward that to the server admin. It’s his presets I am using.

In this case, it were different headers I had to introduce, and turn off Transfer-Encoding. Thank you for directing us in the right direction!