|
<snip> > 1. The stuff comes back HTTP-ized. I'm tired, I can't think of the name > for it, but it's when an angle bracket gets changed to < or >. > I'll have to deal with that. I know that this comment isn't very helpful, but... that's HTML, not HTTP. It's not part of the HTTP standard in any way. If it were HTTP, it would look like "%3c" I would assume that the web service is doing it this way so that it will display the text in a web browser rather than try to interpret it, but, IMHO that's incorrect behavior. It should, instead, return a different content-type than TEXT/HTML. <snip> It's doing it that way because of the XML. <, >, and & have to be escaped when they are sent in XML. If you don't escape those characters, you'll generate invalid XML. Matt
As an Amazon Associate we earn from qualifying purchases.
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.