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



Hi David,

You're right, you should not have to escape the & character if it's within a <![CDATA[ wrapper.

Unfortunately, not every XML parser supports CDATA (especially the very early ones) and if the server is using a home-grown XML interpreter, then all bets are off.

Converting from & to &amp; should work anywhere/everywhere. You should also change < to &lt;, and > to &gt;. There are a few others that are recommended (though not necessarily required) as well.


On 6/4/2012 5:31 PM, David Baugh wrote:
I have a data item on file that I'm inserting into an element before
posting it in a request. In this particular case, the data contains a
'&' which is causing server's parser to error out. I do have it
wrapped in<![CDATA[ ...]]>. Obviously I'm misunderstanding this,
since I thought occurrences of such would be accepted if inside this
wrapper. Can anyone explain why I'm getting a parser error on an '&'
when it's inside the wrapper?

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

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.