RE: ssl_error(406) -- RPG400-L

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

-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of Charles Wilt
Sent: Wednesday, March 31, 2021 4:11 PM
To: RPG programming on IBM i <rpg400-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: ssl_error(406)

Doesn't sound like it's anything SSL related..

You need to look closer at the URL you're getting...

Using any query parms?

Need to URL encode something your not?

Postman can show you the raw request, you should be able to compare to the
raw request in the HTTP API debug logs..

Don't slap yourself too hard when you find it. :)

Charles

On Wed, Mar 31, 2021 at 12:40 PM Greg Wilburn <
gwilburn@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

Scott,

Thank you. With IBM's help I took a TCP trace of the connection. The IBM
Support person read the trace and gave this response:

It shows the connection made and secured, then application data sent, a
response, then application data sent, acked, but no response, and the RST
arrives after 30 seconds. It appears to be an issue on the remote side.

Again, what's weird is when I send the same thing via Postman, I get a
response in less than 3 seconds. So it must be something I'm sending that
it doesn’t' like. I've confirmed the Header information I add in HTTPAPI
matches the corresponding header in Postman.

I'm still waiting to hear back from the web service developers.

Here is a snippet of the debug.txt after the SSL Certificate:

Serial Number: 04:50:9D:7A:C2:6C:2D:71:40:DF:C3:25:37:40:74:36
Common Name: www.meetribbon.com
Issuer CN: Amazon
Issuer Country: US
Issuer Org: Amazon
Issuer Org Unit: Server CA 1B
Version: 3
not before: 20200702200000
Unknown Field: 20:00:00 02-07-2020
not after: 20210803080000
Unknown Field: 08:00:00 03-08-2021
pub key alg: 1.2.840.113549.1.1.1
signature algorithm: 1.2.840.113549.1.1.11
Unknown Field:
0382010F003082010A0282010100B1C2C1189DE0AD3C4A715903D52F86A383ECE0639C53A91EDE27D1B4734C01706D10D7E24F26656B939B77C3467FD37B725A28D517C9EEBDD3CDE9AC3AE65DA710E27C8528AA1912C055A00D4736FCAE38052B3C8D634D84B4F52175E21124BAE50F88AB5DD96134E294092A8E9E11471157247A60A9D0E99A4FCDC6E9FE2C7259636448FB071E53F9CEFDE14744E34ED899EE4BBE0818F6960CA73D685484F87D5E5AE92851E8702A6EDFDBBCA65E4016058BB76F43869A5AE808AD9FE661CD791FC651206CE43F327961A697C831B82BED0F02D6B921B9CD34EB9071249292C73A2C41CFCEA12CE6A5F8ADBB3172705C1CBB707EC3E4312CBEB1F4F58D70770203010001
Unknown Field: 2048
Unknown Field: 3A3691D5DAEFF093C745A8EFDED055E6
Unknown Field: 1.2.840.113549.2.5
Unknown Field: C433C4B7919FDAA3739963339904523C36710A81
Unknown Field:
1DCF1D749E9E773411FF4C848BA94880ACBB695001AD98246FA2967E88BA84B7
Unknown Field: 5
Unknown Field: www.meetribbon.com
Unknown Field: 0
Unknown Field: 1.3.6.1.5.5.7.3.2
Unknown Field: 1.3.6.1.5.5.7.3.1
Unknown Field: 2.23.140.1.2.1
Unknown Field: 2.16.840.1.114412.1.2
Unknown Field: http://ocsp.sca1b.amazontrust.com

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: NSDB2I <removed>
secretToken: LNh+IBj72 <removed>
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

Greg

-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of
Scott Klement
Sent: Tuesday, March 30, 2021 5:36 PM
To: rpg400-l@xxxxxxxxxxxxxxxxxx
Subject: Re: ssl_error(406)

Greg,

If the API developer can help you, that's great.

In my experience, though, they're not usually that helpful. They won't
take things to the level of understanding the specific underlying HTTP
code -- instead, they just tell you to use a tool that they already know
works. I usually have better luck figuring things out myself.

-SK

--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com