> Yes, this flag shall not affect content validity (in this case, the > base64 data), and this behavior is to be changed.
Thank you, if this gets fixed, I owe you a beverage of your choice! > However, I noticed that in the DOM tree, the content > remains unnormlized irregardless of the flag (of course this is not > correct either). I think you can set the normalization on to > get your base64 through and at the mean time still have the > unnormlized data from the DOM tree. Can you elabrate more on this? My code suggest this isn't the case. When I turn the datatype normalize flag on in my parser object, it does in fact change the base64 data placed into the DOM tree (which is certainly expected behavior). When I grab the text node's value, it's definitely normalized. I know this because when I set the flag on (which as you say, does get it past the 2.6 validator), OpenSSL chokes. I pass the node values into OpenSSL calls to create X509 objects, for example, and the missing linefeeds cause the decoder there to complain. The original issue I used to have that caused me to run with normalization off was that signature computation broke. So that also suggests that it is changing the data in the DOM. If you're seeing different behavior, can you send me a test program to try? -- Scott --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
