[I first sent this to the FTPAPI mailing list, but it never showed up there, so I thought I'd try here]

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.

Example of data being returned:
<?xml version="1.0" encoding="utf-8"?>
<string xmlns="http://tempuri.org/";>&lt;?xml version="1.0"?&gt;
&lt;Response xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"&gt;

The procedure I'm calling is http_url_post
I'm not sure if this matters, but:
Content Type: application/x-www-form-urlencoded
User Agent: Apache-HttpClient/4.1.1 (java 1.5)

Do you have any suggestions to prevent the bracket replacement from happening?

I scoured the HTTPAPI source and didn't see come across anything I felt was causing this to happen.


Kurt Anderson
System Development Manager, Service Delivery Platform
web: www.customcall.com<http://www.customcall.com/> | email: kanderson@xxxxxxxxxxxx<mailto:kanderson@xxxxxxxxxxxx>

A Division of Enghouse Systems Ltd.<http://www.enghouse.com/> (TSX:ESL)

[Email Signature - Enghouse Networks Order Management User Forum]<http://bit.ly/2JCjBRI>

This thread ...


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

This mailing list archive is Copyright 1997-2020 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].