Re: ssl_error(406)

[Brad Stone <bvstone@xxxxxxxxx>]

First thing I would do is make sure you have the proper accept header... I
don't see one in your request.  */* usually works.  But application/json is
probably what they're looking for.  I have seen many web APIs puke because
the proper accept header wasn't there.

If that's not it, this reminds me of an issue a couple others of us were
having back in the day that dealt with caching ssl info or something like
that?  It's been a while so I don't recall, but I did have one customer who
worked with IBM when something like this started happening after
applying PTFs.

I'd contact IBM and do some tracing.  I don't think it has anything to do
with HTTPAPI... more likely either the remote system doesn't like what's
happening on the IBM i side of things.

I think there is also lower level debugging.. i didn't see anything about
handshakes in the debug provided.

Brad
www.bvstools.com




On Thu, Apr 1, 2021 at 3:50 PM Greg Wilburn <
gwilburn@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

> Still haven't found it...  literally driving me crazy.
>
> This is from Postman... they do have more things in the header, but
> nothing I can see that would cause the disconnect.  (Auth and Token removed)
>
> GET /v1/orders HTTP/1.1
> Authorization: xxxxxxx
> secretToken: xxxxxx
> vendorID: 5f8a007f71696800d98427b1
> agencyID: 5f077af27d6be71f487bdd34
> User-Agent: PostmanRuntime/7.26.8
> Accept: */*
> Cache-Control: no-cache
> Postman-Token: 791bd877-1b46-47b4-9151-17abaa3435ec
> Host: api.meetribbon.com
> Accept-Encoding: gzip, deflate, br
> Connection: keep-alive
> HTTP/1.1 200 OK
> Content-Type: application/json
> Content-Length: 492155
> Connection: keep-alive
> Date: Thu, 01 Apr 2021 20:42:27 GMT
> x-amzn-RequestId: 20d6fddc-de62-4a89-a6c2-48e5edb3285f
> Access-Control-Allow-Origin: *
> x-amz-apigw-id: dHx4BHEXIAMFbaQ=
> X-Amzn-Trace-Id: Root=1-60663033-689445b2217af86e4e83d55a;Sampled=0
> X-Cache: Miss from cloudfront
> Via: 1.1 502d715ad2f775c7dae1f1c4bfbfc169.cloudfront.net (CloudFront)
> X-Amz-Cf-Pop: EWR52-C4
> X-Amz-Cf-Id: kAPNoCT4qtti3i07pkeXZFeIXJuuxNccGLIwGa5e3A1Dt93U9znpYg==
>
> ...more
>
> This is from the HTTPAPI Debug
>
> SetError() #49: SSL_protocol: Unknown protocol 5000
> Protocol Used:
> http_persist_req(GET) entered.
> http_long_ParseURL(): entered
> http_long_ParseURL(): entered
> do_oper(GET): entered
> There are 0 cookies in the cache
> GET /v1/orders HTTP/1.1
> Host: api.meetribbon.com
> User-Agent: http-api/1.43
> Authorization:  xxxxxxx
> secretToken:  xxxxxxxx
> vendorID:  5f8a007f71696800d98427b1
> agencyID:  5f077af27d6be71f487bdd34
>
> recvresp(): entered
> (GSKit) I/O: A connection with a remote socket was reset by that socket.
> ssl_error(406): (GSKit) I/O: A connection with a remote socket was reset
> by that socket.
> SetError() #44: CommSSL_read:  read:(GSKit) I/O: A connection with a
> remote socket was reset by
> recvresp(): end with err
> http_close(): entered