What are the HTTP headers returned? There should be a content-type
specified there as well.

If you're sending XML, then yes, you should have the proper content-type in
your header as well, and also you may want to make sure you specify the
proper accept header as well.

In this case it doesn't look like all the brackets are being converted,
which is weird. I'd say it's the web service doing that for some reason.

I have a sample URL we can test with, post it to see if others get the same
response.


Bradley V. Stone
www.bvstools.com
MAILTOOL Benefit #16 <https://www.bvstools.com/mailtool.html>: No external
"helper" PC system required. 100% IBM i native!

On Thu, Aug 30, 2018 at 10:55 AM Kurt Anderson <Kurt.Anderson@xxxxxxxxxxxx>
wrote:

Hi David,

I'll play around with that hopefully soon. I was using the content type
that our vendor told us to use.

Kurt Anderson
System Development Manager, Service Delivery Platform

-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxx> On Behalf Of David Gibbs
Sent: Thursday, August 30, 2018 11:20 AM
To: RPG programming on the IBM i (AS/400 and iSeries) <
rpg400-l@xxxxxxxxxxxx>
Subject: Re: HTTPAPI: Output to File changing brackets

On 8/30/2018 9:52 AM, Kurt Anderson wrote:
Recently a vendor of ours changed from providing an on-premise
solution to requiring that we use their web services instead. In
initial testing, I was getting the data response back to the RPG
program directly and everything was fine. However due to the high
volume of data, I now have the API output the data to the IFS, and
then I parse it from there. However, when I have the API output the
file to the IFS, it's replacing the brackets as if it thinks they are
a part of the data. The quick solution was to have the process fix
the brackets, but I feel both the API changing the brackets as well as
me fixing them is taking way too long.

I'm no expert, but I suspect it's because the content type is
'application/x-www-form-urlencoded'.

It should probably be returning 'application/xml' or 'text/xml'.

david

--
David Gibbs
midrange.com

IBM i on Power Systems: For when you can't afford to be out of business!

I'm riding 615 miles (Yes, you read that right) in the American Diabetes
Association's Tour de Cure to raise money for diabetes research, education,
advocacy, and awareness. You can make a tax deductible donation to my ride
by visiting https://lsteml.diabetessucks.net.

See where I get my donations from ... visit
https://lsteml.diabetessucks.net/map for an interactive map (it's a geeky
thing).

I may have diabetes, but diabetes doesn't have me!
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD


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-2019 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].