|
From: Rajesh Ravindran <rajesh.ravi@xxxxxxxxx><web400@xxxxxxxxxxxxxxxxxx>
To: "Web Enabling the IBM i (AS/400 and iSeries)"
Date: 07/28/2020 02:08 PMdata
Subject: [EXTERNAL] Re: [WEB400] IWS, REST and retrieving variables
from QUERY_STRING
Sent by: "WEB400" <web400-bounces@xxxxxxxxxxxxxxxxxx>
Hi Nadir, is there a plan to support mapping path/query parameters to
structures and its subfields?the
Most of the APIs have multiple query/path parameters so we end up using
alternate approach getenv() to receive the entire query/path string andparameter
parse it
Thanks,
Rajesh
On Tue, Jul 28, 2020 at 1:51 PM Nadir Amra <amra@xxxxxxxxxx> wrote:
Hi,
You have two options to getting access to query string variable. The
recommended way is to inject the query string parameter into a
environmentautomatically.
The alternative way is to pass the entire query string as an
andvariable and within your code you would need to issue a getenv() call
08:45:55then parse the query string variable.
Obviously, injecting an input parameter with value of query string
variable is easiest. And this method allows you to specify a default
value as well if not specified.
"WEB400" <web400-bounces@xxxxxxxxxxxxxxxxxx> wrote on 07/28/2020
serviceAM:
From: Robert Rogerson <rogersonra@xxxxxxxxx><web400@xxxxxxxxxxxxxxxxxx>
To: "Web Enabling the IBM i (AS/400 and iSeries)"
Date: 07/28/2020 08:46 AMPostman
Subject: [EXTERNAL] [WEB400] IWS, REST and retrieving variables from
QUERY_STRING
Sent by: "WEB400" <web400-bounces@xxxxxxxxxxxxxxxxxx>
Hi All,
I'm creating a REST webservice/api and using IWS. I'm then using
to test the webservice. All the endpoints call procedures in a
procedureprogram..
I have an endpoint /web/server/claims which will call the RPG
PostmanGetAllClaims which returns all claims. I have tested this with
thisand it works correctly.
My next step is to add a filter. So I call the same endpoint but
QUERY_STRINGtime
I pass a parameter of whid. So the endpoint now becomesGetAllClaims
/web/server/claims/?whid=93 which will call the RPG procedure
but this time I need to extract the parameter passed in the
searchingto
return only claims for warehouse 93.
Can someone point me to either documentation or an example of how to
specify and extract from the QUERY_STRING. I've done a lot of
can'ton
Google but I must not be searching on the correct terms because I
mailingfind anything on QUERY_STRING other than that you may specify it..
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400)
u=https-3A__lists.midrange.com_mailman_listinfo_web400&d=DwICAg&c=jf_iaSHvJObTbx-list
To post a message email: WEB400@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://urldefense.proofpoint.com/v2/url?
siA1ZOg&r=1i-jGlz0-JTK1aLHcsU-ew&m=sPmGnTZ0_vyJ3_54kaOu8o5l9td1XfdHry9XmoY7Hl8&s=Vc0Krx2AKMB8BSPQOiJOivd13RRfExPAJK597kNhI5w&e=
ew&m=sPmGnTZ0_vyJ3_54kaOu8o5l9td1XfdHry9XmoY7Hl8&s=-
PbZhPcHTyVMSaH244SWbnNivDS1mOGhO_HUWXKQj8g&e=
or email: WEB400-request@xxxxxxxxxxxxxxxxxxu=https-3A__archive.midrange.com_web400&d=DwICAg&c=jf_iaSHvJObTbx-
Before posting, please take a moment to review the archives
at https://urldefense.proofpoint.com/v2/url?
siA1ZOg&r=1i-jGlz0-JTK1aLHcsU-
.list
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
To post a message email: WEB400@xxxxxxxxxxxxxxxxxxu=https-3A__lists.midrange.com_mailman_listinfo_web400&d=DwICAg&c=jf_iaSHvJObTbx-
To subscribe, unsubscribe, or change list options,
visit: https://urldefense.proofpoint.com/v2/url?
siA1ZOg&r=1i-jGlz0-JTK1aLHcsU-ew&m=sPmGnTZ0_vyJ3_54kaOu8o5l9td1XfdHry9XmoY7Hl8&s=Vc0Krx2AKMB8BSPQOiJOivd13RRfExPAJK597kNhI5w&e=
ew&m=sPmGnTZ0_vyJ3_54kaOu8o5l9td1XfdHry9XmoY7Hl8&s=-
PbZhPcHTyVMSaH244SWbnNivDS1mOGhO_HUWXKQj8g&e=
or email: WEB400-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://urldefense.proofpoint.com/v2/url?
u=https-3A__archive.midrange.com_web400&d=DwICAg&c=jf_iaSHvJObTbx-
siA1ZOg&r=1i-jGlz0-JTK1aLHcsU-
.
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.