Re: QSYS2.HTTP_GET problem with the USPS APIs -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: QSYS2.HTTP_GET problem with the USPS APIs
From: Jack Woehr <jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx>
Date: Tue, 4 Jan 2022 20:21:41 -0700
List-archive: <https://archive.midrange.com/midrange-l/>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

We can debug this, but rather than debugging the arcana of Db2, why not
just call curl in PASE and pass the info back to the caller>?

On Tue, Jan 4, 2022 at 6:52 PM Sam_L <lennon_s_j@xxxxxxxxxxx> wrote:

Fighting with all kinds of new things...

** CURL in Ubuntu: This works.

** CURL in QP2TERM on Pub400.com: Works, using the above command.

** QSYS2.HTTP_GET on PUB400.com: FAILS (using the same big ugly string.)

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: QSYS2.HTTP_GET problem with the USPS APIs , Sam_L

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.