RE: HTTPAPI failing -suspect TLS -- MIDRANGE-L

Subject: RE: HTTPAPI failing -suspect TLS
From: Chris Bipes <chris.bipes@xxxxxxxxxxxxxxx>
Date: Tue, 26 Jul 2016 18:48:09 +0000
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Question. How can I determine the version of LIBHTTP?

Chris Bipes
Director of Information Services
CrossCheck, Inc.

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Tuesday, July 26, 2016 11:32 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: HTTPAPI failing -suspect TLS

Peter,

Please make sure you are using an up-to-date version of HTTPAPI. Older
versions would not have supported TLS 1.1 or 1.2 on V7R1.

Its funny that you tell us the versions of everything except HTTPAPI...

CURL and Node.js are not good tests, here, as they use open source SSL
libraries in PASE rather than the native ones that IBM provides with IBM i.

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: HTTPAPI failing -suspect TLS , Scott Klement

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.