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

Seems like you're not checking that the buffer isn't empty before trying to
use it...
assuming you're using the "peSaveProc" parm of http_persist_req().

If you're expecting the reply to be saved to a stream file via the
"peSaveFD", then maybe it's something in HTTP API.
Though I'd be sure to check that the FD is opened correctly before the call.

Charles

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

On 8/8/23 5:30 PM, Scott Klement wrote:

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

And *what* value would that be? RC is coming back as 1; otherwise
(whitespace squeezed out for email purposes)

C IF RC <> 1
C EVAL BUFFY=http_error
C EVAL M$G=http_error
C M$G DSPLY
C SETON LRH1
C RETURN
C ENDIF

would have tripped.

Given that return code, so far as *the program* knows, either everything
is hunky-dory, or the *web service itself* complained in the reply. It's
only when the program tries to parse the reply buffer, and finds it
completely empty, that it blows up, and it was only when I saw the debug
file that I had any indication that the SSL handshake had failed in some
way.

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