You need to have some sort of delimiter between the variables, something
like:

/{program}/{section}/{user}/{log}

or something like:

/{program}-{section}-{user}-{log}

The way you have it there is no way to determine where program begins and
where section begins, etc.

Then in url,

/program/section/user/log

or

/program-section-user-log

Now whether the URI is appropriate is up to you, based on documentation I
referenced and common practices.

"WEB400" <web400-bounces@xxxxxxxxxxxxxxxxxx> wrote on 08/12/2019 04:58:06
PM:

From: Booth Martin <booth@xxxxxxxxxxxx>
To: "Web Enabling the IBM i (AS/400 and iSeries)"
<web400@xxxxxxxxxxxxxxxxxx>
Date: 08/12/2019 04:58 PM
Subject: [EXTERNAL] Re: [WEB400] IWS - how to specify more than one
input parameter
Sent by: "WEB400" <web400-bounces@xxxxxxxxxxxxxxxxxx>

Nadir, yes. I have read that (many times) and done that several times.

The IWS server appears to me to not be handling it correctly. I think
it's a pretty safe bet that the problem is NOT in the IWS server, but in

how I am using it.

It's pretty likely the problem lays with something I am not
understanding. At the moment I suspect it's that i am messing up the
"URI path template" on Step 1 of 7 in the IWS interview?

I have

/{program}{section}{user}{log}

Is that the proper use of the URI path template?


On 8/12/2019 3:06 PM, Nadir Amra wrote:
As far as what URIs should look like, see page 36 of IWS server admin
and
programming guide[1], heading entitled: "REST Primer". It has sections
about URIs and the user of HTTP methods.


[1]http://www.ibm.com/support/docview.wss?uid=isg3T1026868





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

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.