Diagnostics returned nothing useful. Just that the UDF returned with a warning.

Am 15. Januar 2019 20:06:32 MEZ schrieb Justin Taylor <JUSTIN@xxxxxxxxxxxxx>:
Does this give anything useful?

-----Original Message-----
From: Mihael Schmidt [mailto:mihael@xxxxxxxxxxxxxx]
Sent: Tuesday, January 15, 2019 11:07 AM
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: HTTP response message null when HTTP Status Code >= 300

Hi folks,

anybody some experience with the SQL HTTP functions? I am using
SYSTOOLS.HTTPGETCLOBVERBOSE. But how do I get the content of the
response message in an "error" case (f. e. HTTP Status Code 400 - Bad

|exec sql SELECT responsemsg, responsehttpheader INTO :responseMessage
:responseMessageNull, :responseHeaderXml FROM TABLE(
SYSTOOLS.HTTPGETCLOBVERBOSE(:wsUrl, :requestHeader)) AS t; |||

Everything works fine if the HTTP response has a status >= 200 and <
300 but else I get null in responsemsg. How do I get the message
content when the HTTP response is not ok (HTTP status code >= 300)?

... and yes, the web service really returns data in the message body. I
made the same request with curl.

Thanks in advance.



This is the RPG programming on the IBM i (AS/400 and iSeries)
(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@xxxxxxxxxxxx for any subscription related

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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