mark, There is nothing special with https. Assume you already have a certificate in the user keyring and use default port 443, you need to perform the following sequence of commands:
Address HWTHTTP "HWTHSET" "HWTH_OPT_USE_SSL " Address HWTHTTP "HWTHSET" "HWTH_OPT_SSLVERSION " with the TLS version like "HWTH_SSLVERSION_TLSv12" Address HWTHTTP "HWTHSET" "HWTH_OPT_SSLKEYTYPE " "HWTH_SSLKEYTYPE_KEYRINGNAME " with the user keyring name Address HWTHTTP "HWTHSET " "HWTH_OPT_SSLKEY " such as userid/keyring ITschak On Mon, Jul 15, 2019 at 3:28 PM Mark Eddy < 000002582cc49a49-dmarc-requ...@listserv.ua.edu> wrote: > I am working with the z/OS Client Web Enablement Toolkit in REXX > attempting to get a sample to send a HTTPS request. > I see that Galina Gorelik posted this statement on Wed, 24 Oct 2018: > We understand that having a working sample is a priority to you and we are > working on getting the sample updated as soon as we possibly can. > We hope to have something shipped very soon. > Have there been any updates to the samples or new samples released since > Oct 2018 that could help? > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- ITschak Mugzach *|** IronSphere Platform* *|* *Information Security Contiguous Monitoring for Legacy **| * ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
