in reply to Re^2: XML Parsing from URL
in thread SOLVED: XML Parsing from URL

This "boundary" stuff and the two "Content"-lines look like HTTP multipart POST data (RFC2388) to me. On the other hand, HTTP POST data should also have a "Content-Disposition" header with a name attribute after each boundary.

Is this real data or shortened? Where does the data come from?

In a HTTP context, I would expect some library to parse the HTTP data and provide them in a more accessible form. For example, using the classic CGI module, each XML document would be available by its parameter name using the param() or upload() methods.


Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)