DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=44177>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=44177 ------- Additional Comments From [EMAIL PROTECTED] 2008-01-07 11:11 ------- (In reply to comment #0) > When signature has xslt transformation reference, there is a problem, because > xalan changes new lines in transformed output to \n on linux and \r\n on > windows, regardles of newline type in input file. Consequence is that > signature > is invalid when validating on different OS. This should be consistent > everywhere > if signature is to be valid. > > You could use something like > Transformer.setOutputProperty("{http://xml.apache.org/xalan}line-separator","\n";); > > .Net uses \n as newline separator when using xslt transformation. > > But what does w3c standard say ? Section 6.6.5 [1] of the XMLDSig W3C recommendation says: "The output of this transform is an octet stream. The processing rules for the XSL style sheet or transform element are stated in the XSLT specification [XSLT]. We RECOMMEND that XSLT transform authors use an output method of xml for XML and HTML. As XSLT implementations do not produce consistent serializations of their output, we further RECOMMEND inserting a transform after the XSLT transform to canonicalize the output. These steps will help to ensure interoperability of the resulting signatures among applications that support the XSLT transform. Note that if the output is actually HTML, then the result of these steps is logically equivalent [XHTML]." Try adding a C14N Transform after the XSLT Transform. [1] http://www.w3.org/TR/xmldsig-core/#sec-XSLT -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
