It can look properly encoded but it won't necessarily be delivered properly encoded to the browser unless the file on the IFS is created with the right ccsid. We have static files that are ok in every browser except IE unless the file encoding on the IFS is 1208. I haven't properly determined why, but is one of the reasons why data shouldn't be delivered in this way.

[] ƕ
On 12 Nov 2016, at 15:47, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

For som reason fixed xml/json files from IBM I apache failes in IE.

Okay. I understand that "encoding" matters. Are the errors limited to
certain characters?

IE takes the answer from responseText and treat it as a 'no string'
making JSON.parse and other DOM commands fail.

As an alternative to JSON.parse you might try something like:

s = 'us_presidents = ' + json; // where "json" refers to an array object.

eval(s); // creates us_presidents object.

In Booth's case, the JSON seems to be properly encoded and well-formed.
So... must be a different problem.
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,
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives

The information transmitted herein is intended only for the person or entity to which it is addressed and may contain confidential, proprietary and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

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