Re: IWS, REST APIs, and Logging

True. I agree that it would diminish the value of IWS. I was hoping that turning on some logging, etc would allow us to capture the payload/body IF it was 'malformed' and it can't unpack into the parameters.

-----Original Message-----
From: WEB400 <web400-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Jon Paris
Sent: Tuesday, April 27, 2021 11:02 AM
To: Web Enabling the IBM i (AS/400 and iSeries) <web400@xxxxxxxxxxxxxxxxxx>
Subject: Re: [WEB400] IWS, REST APIs, and Logging

Well it kinda goes against the whole point of IWS which is to avoid you having to concern your self with such issues. The payload is unpacked into the parameters and vice-versa for you.

If you really need to access the body why use IWS at all?



Jon Paris

On Apr 27, 2021, at 11:23 AM, Stephen Piland <Stephen@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

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: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxxxxxxxx Before posting, please
take a moment to review the archives at
https://archive.midrange.com/web400.

--
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: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxxxxxxxx Before posting, please take a moment to review the archives at https://archive.midrange.com/web400.