> Is this the way things ought to be, or should the canonicalization be
> checking the namespace and prefix components on each element, and
including
> an xmlns attribute when any change occurs between an element and its
parent?
I'm not certain, but I don't think that's actually part of the spec.
pect that in the first instance, the profix was being
> resolved by climbing the tree enclosing the decrypted looking for an
> xmlns:sp, and finding it on the element enclosing the encrypted payload.
>
> Has this behaviour been seen before?
>
>
--
View this message in context:
http://www.nabble.com/Unbound-prefix-after-decryption-tp19626544p19659756.html
Sent from the Apache XML - Security - Dev mailing list archive at Nabble.com.
was being resolved
by climbing the tree enclosing the decrypted looking for an xmlns:sp, and
finding it on the element enclosing the encrypted payload.
Has this behaviour been seen before?
--
View this message in context:
http://www.nabble.com/Unbound-prefix-after-decryption-tp19626544p196
