Re: Qsys2.http_post

The usual cause is the fact that the old tools used the Java certs - but the new one uses the system certs. Unless you have taken steps to populate the *System store with the needed certs a number of services will not work.

This was discussed here on the Midrange list last week. Here's the relevant links that I found useful.

Check out this page https://www.ibm.com/docs/en/i/7.5?topic=programming-http-functions-overview and in particular the section under SSL Considerations. It explains the differences and provides a script to import all of the Java DCM certs into the *System store. Although a much easier way is to use Jesse's tool - you'll see the reference to my issues in this thread. https://github.com/ThePrez/DCM-tools/issues/32

The net is that we had a LOT of examples that would not run under the new stuff for this reason. The Java store includes all the stuff like Amazon and others that the default system store does not have. Once we imported everything from the Java store it all worked again.


Jon P.

.

On May 9, 2023, at 5:56 AM, Jay Vaughn <jeffersonvaughn@xxxxxxxxx> wrote:

can someone tell me why when I use the qsys2.http_post below (uncomment out the qsys2.http_post and header parm) it will not work... but works fine with systools.httpgetclob?



select *
from json_table(
-- qsys2.http_post('https://api.mapbox.com/geocoding/v5/mapbox.places/Mobile' concat
systools.httpgetclob('https://api.mapbox.com/geocoding/v5/mapbox.places/Mobile' concat
'.json?access_token=' concat
'myKey' concat
'&limit=1'
,cast(null as clob(1k))
-- ,'{"header":"content-type,application/x-www-form-urlencode","sslTolerate":"true"}'
)
,'$' columns (
Lat float path '$.features[0].center[1]'
,Lon FLOAT path '$.features[0].center[0]'
,PName CHAR(100) path '$.features[0].place_name'
) error on error
) as x;


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