(cross-posted from Scott's HTTPAPI list) I need the SSL version [of HTTPAPIR4] to be backward-compatible with programs expecting the non-SSL version. -- MIDRANGE-L

Subject: (cross-posted from Scott's HTTPAPI list) I need the SSL version [of HTTPAPIR4] to be backward-compatible with programs expecting the non-SSL version.
From: James Lampert <jamesl@xxxxxxxxxxxxxxxxx>
Date: Wed, 28 Dec 2011 08:50:51 -0800
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/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

We already have programs that depend on the non-SSL version of
HTTPAPIR4, while the new programs I'm working on (calling Google web services) need the SSL version.

Toward this end, and following the "Binder Language" section of the ILE
Concepts book, I tried adding the STRPGMEXP block from the HTTPAPI1
member to the HTTPAPI2 member [of LIBHTTP/QSRVSRC], as a *PRV STRPGMEXP block; I recompiled, and when the program expecting the non-SSL version tried to use it, it got an MCH3601 at a call to "http_url_get_raw."

Any clue what could have gone wrong?

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 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.