Re: Setting up a web services server, and services

Thanks for the explanation.

The web services I have deployed to-date have used an HTTP server and not an app server.

I have experimentally used the IWS server but did not recall the paths being case-sensitive.

Now that some of the redeployment issues with the IWS setup have been resolved I will revisit it.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Nov 23, 2018, at 1:57 PM, Nadir Amra <amra@xxxxxxxxxx> wrote:

Its not the wizard that does the mapping. It is the application server.
And application servers deal with context root for a resource, which is
case sensitive. HTTP servers deal with paths to a resource. So mapping
is different. HTTP servers determine if a resource exists by checking the
path to the resource (normally by using an IFS API to read the resource.
Application servers already know what resources exist via context root.

Not saying it would not be a good idea to indicate context root is
case-insensitive. But not in IWS control.

"WEB400" <web400-bounces@xxxxxxxxxxxx> wrote on 11/23/2018 12:44:09 PM:

From: Jon Paris <jon.paris@xxxxxxxxxxxxxx>
To: "Web400@Midrange. Web400" <web400@xxxxxxxxxxxx>
Date: 11/23/2018 12:44 PM
Subject: Re: [WEB400] Setting up a web services server, and services
Sent by: "WEB400" <web400-bounces@xxxxxxxxxxxx>

Which I think is what I alluded to earlier.

So why does the wizard not offer that as a deployment option?


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/web400.