Peter, I have resolved the issue. It turns out that when I was adding a character set to our application (so users could enter French/Latin characters), I used the old System.useCodePage trick from my days as a Flash developer... when that property is set to true, the extra characters get appended to the end of the HTTPService results I suspect due to the servlets being UTF-8 (not Unicode) -- I could be wrong about the specifics.
Thank you very much for your help though. Brian --- In [email protected], "Peter Farland" <[EMAIL PROTECTED]> wrote: > > > I don't believe there is a maximum length (or at least the length you > describe is surely not a problem in itself), however if you are using > chunked encoding then the length of the document will change the way the > data is sent (i.e. chunked or not). > > On reading that you were dealing with chunked data, it reminded me of a > known issue (Bug 191814) with the Flash Player in MSIE. The issue occurs > when a Cache-Control: no-cache header is sent but with chunked encoding > and gzip'ed content. > > I believe a work around is to append "must-revalidate" to the > Cache-Control no-cache header: > > Cache-Control: no-cache, must-revalidate > > This Microsoft KB article > http://support.microsoft.com/kb/871205 > mentions the issue occurs with HTTPS, but we've seen reports with HTTP > too. > > Pete > > ________________________________ > > From: [email protected] [mailto:[EMAIL PROTECTED] On > Behalf Of klumikaze > Sent: Tuesday, March 06, 2007 12:21 PM > To: [email protected] > Subject: [flexcoders] Re: Special characters after end tag of XML > document (HTTPService issue) > > > > Peter, > > We've installed TamperData for Firefox and we've done some extensive > testing with it to > see if the special characters exist in the HTTP responses. We have been > unable to > reproduce the problem there. We have tried setting the content length > header accurately > based on the data the servlet spits out. We have also checked the other > items you > suggested and they appear to be fine... we are actually just generating > a string of XML > manually, there is no XML document in the equation. > > At this point we are wondering what the possibility is that the > HTTPService (or URLLoader) > has problems handling chunked data? Is there a maximum length that the > HTTPService/ > URLLoader can handle for an XML document? Our average document is > sitting at around > 500 lines of XML. > > Thanks again for your assistance with this issue, > > Brian >
