Re: [EXTERNAL] Re: Problem with proof of concept program utilizing IWS (Integrated Web Services) -- MIDRANGE-L

× 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.

Thanks for the update, Alan. For those of us who are a bit slower, which change did you make? *ALL or application/json?

Glad it worked!

On 2/19/2019 1:37 PM, Alan Shore via MIDRANGE-L wrote:

I want to thank everyone who were courteous to answer my e-mail
Nadir pointed out what my problem was
In creating the REST service he saw what I was doing wrong (I sent him my document (offline) as to the steps that I had taken)

Here is the response he sent me

When you deployed, you specified on the "Allowed input media types" the value of JSON. If you do this via browser, there is no way to specify incoming media type. By default, for GET requests, there is no payload and thus no media and thus no content-type HTTP header (I think the default content type is text/plain). If you had specified *ALL then it would have worked. Otherwise, from SOAPUI, you would need to add content-type header on the request and specify application/json.

Let me know how it goes.

Once I made the change - I was able to process the web page and receive responses

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.