Re: SSL handshake error/timeout in HTTPAPI: is there a way to catch this and recover?

As you already know, it returns a value that indicates that the request
failed.

So... when you get them, you can call the routine again to try
again... Not sure what you're looking for that you don't already know?

On 8/8/2023 5:14 PM, James H. H. Lampert via MIDRANGE-L wrote:

I have a program that calls HTTPAPI (yes, I know, I seem to have a lot
of them), and a few minutes ago, it crashed while trying to parse an
empty reply buffer, with (and I should have saved the
/tmp/httpapi_debug.txt) something about an SSL handshake timeout as
the last debug message.

The last HTTPAPI call was an "http_persist_req" with an opcode of
"PUT." The return code came back as 1, but the program got an empty
reply buffer.

I suspect that another program on another customer box, that recently
crashed with a return code of 1 but an empty reply buffer, suffered
the same fate, but the debug file had already been overwritten before
anybody told me there was a problem.

Is there a way for the calling program to detect SSL handshake
failures, so it can recover from them?

--
JHHL

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.