MvCALL: SSL Read Timeout

[ids]

UPDATE: Changing from RAW to POST seems to have solved the connection issue.

UPDATE/UPDATE: Solved. The specs for the server application are missing critical information and explanation. Turned out that the URL needed a specific name=value pair to understand what the data in the request was.

My conclusion so far is that this server instance is expecting the payload differently than the RAW method supplies it. Is MvCall, using POST, conditioning the payload in some way?

ALSO and related: The payload data appears to be interpreted as encoded and the server isn't recognizing the JSON string in the request as a JSON string. It responds with an encoded version of the string. What do I need to do to the string to "protect" it? BTW: I have a Content-Type of application/json in the header.

Scott

[dcarver]

No it wouldn't matter at all.

[ids]

OK, Thanks for the responses.

Long shot question: Would it matter in anyway if the server being called is a MS Windows type of server?

Scott

[dcarver]

A read timeout would occur if we are not getting a response from the remote server. So either initial connection failed or after we have sent the data they have not responded.

[ILoveHostasaurus]

It means either the remote server is unreachable in a way that it hangs instead of fails, or it was reachable but didn’t respond before the timeout was reached.

[ids]

Any help on why I am getting this error?

The URL in the Call is exactly what is specified, and it is https. The JSON payload to this server is what I am told a working sample. I've validated it also. Not sure where to start looking for the issue.

BTW: the JSON is using variables and I think they are using "mustache" formatting, not positive. So, the server appears to handle this, but, can the MvCall send the payload correctly? Because it always works for this "POST," MvCall is configured as RAW. I haven't tried a GET or POST.

Scott