Re: IWS, REST APIs, and Logging

At this time logging payloads is not supported. Although there are plans
on implementing this.

You can do a trick where you have input parameter that is of character
type and not injected from any input source, with a length large enough to
handle input request, and best to make it varchar.

Then any REST requests that are inbound will be put into the parameter
as-is. It will not be parsed. Thus, it is up to you to do the parsing.


"WEB400" <web400-bounces@xxxxxxxxxxxxxxxxxx> wrote on 04/27/2021 10:23:55
AM:

From: Stephen Piland <Stephen@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
To: "web400@xxxxxxxxxxxxxxxxxx" <web400@xxxxxxxxxxxxxxxxxx>
Date: 04/27/2021 10:24 AM
Subject: [EXTERNAL] [WEB400] IWS, REST APIs, and Logging
Sent by: "WEB400" <web400-bounces@xxxxxxxxxxxxxxxxxx>

I haven't seen any way to do this so far, but I thought I'd ask the

group...

Is there any way to capture the 'payload'/body sent in? Ideally,
pre-execution of the program or service program call from within
IWS. If not, is there a way to capture it in the called pgm perhaps
as a BLOB that could be stored?

Thanks!
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing

list

To post a message email: WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: INVALID URI REMOVED

u=https-3A__lists.midrange.com_mailman_listinfo_web400&d=DwICAg&c=jf_iaSHvJObTbx-

siA1ZOg&r=1i-jGlz0-JTK1aLHcsU-ew&m=3Dw-
cTFEmzY4eWlRdl1JWhz357r3x0udln7hpjlYKSU&s=JAlDNR9N2juI8XepE5U2XJ7-
MBYwi_lA0AAxEOZSfME&e=
or email: WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at INVALID URI REMOVED
u=https-3A__archive.midrange.com_web400&d=DwICAg&c=jf_iaSHvJObTbx-
siA1ZOg&r=1i-jGlz0-JTK1aLHcsU-ew&m=3Dw-

cTFEmzY4eWlRdl1JWhz357r3x0udln7hpjlYKSU&s=_C2FZiH6EADG9G10z_mUUSuGZauTg00Z0rGlEuZCQq8&e=

.