Re: REST API and QUERY_PARM -- WEB400

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: REST API and QUERY_PARM
From: Stephen Piland <Stephen@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Date: Tue, 2 Apr 2019 17:40:11 +0000
List-archive: <https://archive.midrange.com/web400/>
List-help: <mailto:web400-request@lists.midrange.com?subject=help>
List-id: "Web Enabling the IBM i \(AS/400 and iSeries\)" <web400.lists.midrange.com>
List-post: <mailto:web400@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/web400>, <mailto:web400-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/web400>, <mailto:web400-request@lists.midrange.com?subject=unsubscribe>

I was trying QUERY_PARM vs PATH_PATH to try and get around my varchar issue. I have an input parm of OrderNo on a GET which I'd like to be varchar(20) but I'm still waiting on PTFs for IWS and HTTP Admin to be applied. I was hoping I'd get passed the string and I could grab order out of it, but I guess the 2 methods are very similar to each other as you stated.

Thanks.

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.