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

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

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 mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.