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

Turn off everything except SSL (ie, no TLS versions) in the system values
and you'll probably get handshake errors up the wazoo for newer connections.

On Wed, Aug 9, 2023 at 1:09 PM James H. H. Lampert via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

On 8/9/23 9:17 AM, Charles Wilt wrote:

Something doesn't make sense here...

an SSL handshake timeout error would only occur during

http_persist_open().

Are you checking for a non-NULL pointer being returned after the open,
before trying to do the http_persist_req()?

THAT'S IT!

I *do* check for whether I have a non-null wwComm returned from
http_persist_open, before I do the http_persist_req or the
http_persist_close, but I *don't* take any further action on that before
I try to HTTP_xlatep and parse an empty buffer.

Thanks, Mr. Wilt.

Maybe it's time I found another line of work better suited to my
complete and utter idiocy.

I don't suppose anybody could suggest the easiest way to force an SSL
handshake timeout? Maybe trying to connect to a nonexistent URL?

--
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.