I was just testing with the recommended 6.12.26 release (which I should've done earlier) and I noticed that the contents of opaque is still wrapped in a CDATA field. This is now causing serious problems with BAM! because every time a host connects it gets a new ID. It's not valid XML so my script can't find the host_authenticator.
I will work around it again, but I'm not happy that this made it into the recommended release. Willy. On Tue, Mar 8, 2011 at 9:34 PM, David Anderson <[email protected]>wrote: > OK, I removed the CDATA > (this will appear in the next 6.12 release) > > > On 07-Mar-2011 10:06 PM, Willy wrote: > >> David, >> >> In the release notes of 6.12.17 release notes it says: >> - client: surround the opaque field in a CDATA block. >> >> As I told you that will make the whole opaque a CDATA field and it will >> break >> BAM! again because the contents of opaque will be considered as text, not >> as XML. >> >> The correct solution would be not to mess up the tags. >> >> I also made a fix at my side which works very will with the old clients. >> >> If you do this: >> <![CDATA[ >> <opaque> >> <host_authenticator>c19befab915c848625c85adc32ddc8ea</host_authenticator> >> </opaque> >> ]]> >> then there is no opaque element in the parsed xml. >> >> If you do this: >> <opaque> >> <![CDATA[ >> <host_authenticator>c19befab915c848625c85adc32ddc8ea</host_authenticator> >> ]]> >> </opaque> >> then the contents of opaque is empty. >> >> Both with PHP's build in XML functions. >> >> Willy. >> >> On Wed, Feb 23, 2011 at 2:07 AM, David Anderson <[email protected] >> <mailto:[email protected]>> wrote: >> >> I added <?xml version="1.0" encoding="UTF-8" ?> >> to account manager request messages >> (this will appear in the 6.14 client) >> -- David >> >> >> On 22-Feb-2011 4:37 AM, Willy wrote: >> >> Is the XML send by the client UTF-8 or another encoding? The second >> most >> reported error with the xml is "Input is not proper UTF-8, indicate >> encoding !" >> with error originating from the domain_name tag contents. >> >> Willy. >> >> On Tue, Feb 22, 2011 at 9:13 AM, David Anderson < >> [email protected] >> <mailto:[email protected]> >> <mailto:[email protected] <mailto:[email protected]>>> >> wrote: >> >> As far as I can tell, only the tag >> (and apparently only the closing tag) >> >> The reason for this: I was using something like >> strcpy(p, p+4) >> to remove characters from the start of a string. >> It turns out that in recent libc on 64-bit Linux, >> this doesn't work - it mangles the string. >> (in fact, strcpy() is not supposed to be used for overlapping >> strings). >> >> -- David >> >> >> On 21-Feb-2011 11:18 PM, Willy wrote: >> >> Is the contents (the authenticator itself) also mangled or >> only >> the tags? >> >> Willy. >> >> On Tue, Feb 22, 2011 at 7:32 AM, David Anderson >> <[email protected] <mailto:[email protected]> >> <mailto:[email protected] <mailto:[email protected]>> >> <mailto:[email protected] <mailto:[email protected]> >> <mailto:[email protected] <mailto:[email protected]>>>> >> wrote: >> >> Now I know what the problem is. >> Because of a bug in the BOINC client, >> some clients will send account manager requests >> with one or more of the XML tags in <opaque> slightly >> mangled. >> >> This problem is fixed in the current development >> release. >> >> To deal with the existing clients, unfortunately, >> you'll need to do something at your end, >> like removing the <opaque>...</opaque> element before >> parsing the request message, >> and then trying to parse the contents of <opaque> >> manually. >> Sorry about that. >> >> -- David >> >> >> On 21-Feb-2011 10:00 PM, Willy wrote: >> >> David, >> >> Check this thread (second post): >> http://boincstats.com/forum/forum_thread.php?id=5198. Other users >> in various >> other threads came to the same conclusion that it >> only >> Ubuntu >> hosts that >> have >> problems. >> >> I have turned logging for bad requests back on to >> see if >> I can >> extract >> the OS >> for the systems with errors. >> >> Willy. >> >> On Mon, Feb 21, 2011 at 11:25 PM, David Anderson >> <[email protected] <mailto:[email protected]> >> <mailto:[email protected] <mailto:[email protected]>> >> <mailto:[email protected] <mailto:[email protected]> >> <mailto:[email protected] <mailto:[email protected]>>> >> <mailto:[email protected] <mailto:[email protected]> >> <mailto:[email protected] <mailto:[email protected]>> >> <mailto:[email protected] <mailto:[email protected]> >> <mailto:[email protected] <mailto:[email protected]>>>>> >> wrote: >> >> Willy: >> It looks to me like BOINCstats is or was >> returning >> bad XML in the <opaque> field. >> You'll probably have to write code to repair >> the XML >> before >> parsing it. >> >> I think that in the future it would be better >> to put the >> <opaque> >> data within a <![CDATA[. >> That way the request message would parse even >> if the >> opaque >> data is bad. >> Does this seem reasonable to you? >> >> -- David >> >> -------- Original Message -------- >> Subject: Re: [BOINC] #1044: Boinc creates badly >> formatted >> xml files >> Date: Mon, 21 Feb 2011 21:41:06 -0000 >> From: BOINC <[email protected] >> <mailto:[email protected]> >> <mailto:[email protected] <mailto:[email protected]>> >> <mailto:[email protected] <mailto:[email protected]> >> <mailto:[email protected] <mailto:[email protected]>>> >> <mailto:[email protected] <mailto:[email protected]> >> <mailto:[email protected] <mailto:[email protected]>> >> <mailto:[email protected] <mailto:[email protected]> >> <mailto:[email protected] <mailto:[email protected]>>>>> >> Reply-To: [email protected] >> <mailto:[email protected]> >> <mailto:[email protected] <mailto: >> [email protected]>> >> <mailto:[email protected] <mailto: >> [email protected]> >> <mailto:[email protected] <mailto: >> [email protected]>>> >> <mailto:[email protected] <mailto: >> [email protected]> >> <mailto:[email protected] <mailto: >> [email protected]>> >> <mailto:[email protected] <mailto: >> [email protected]> >> <mailto:[email protected] <mailto: >> [email protected]>>>> >> >> >> #1044: Boinc creates badly formatted xml files >> >> >> >> >> ------------------------------------+--------------------------------------- >> Reporter: LiSrt | >> Owner: >> davea >> Type: Defect | >> Status: new >> Priority: Major | >> Milestone: >> Undetermined >> Component: Account Manager System | >> Version: >> 6.10.58 >> Keywords: xml host_authentictoor | >> >> >> >> >> ------------------------------------+--------------------------------------- >> Changes (by LiSrt): >> >> * owner: => davea >> * priority: Undetermined => Major >> * component: Undetermined => Account Manager >> System >> >> >> Comment: >> >> This is also described on the boincstats >> forum >> [ >> http://boincstats.com/forum/forum_thread.php?id=5198] >> >> I selected "Major" because it appears to >> prevent >> account >> manager >> synchronisation. >> >> -- >> Ticket URL: >> <http://boinc.berkeley.edu/trac/ticket/1044#comment:1> >> BOINC <http://boinc.berkeley.edu> >> Berkeley Open Infrastructure for Network >> Computing >> (BOINC) >> >> >> >> >> >> _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
