OASIS Open Mailing List Archives  ·  All Lists  ·  ebxml-msg  ·  2002-01

ebxml-msg — archive

[Date Prev]  |  [Thread Prev]  |  [Thread Next]  |  [Date Next]   —  [Date Index]  |  [Thread Index]  |  [Month Index]  |  [List Home]

RE: [ebxml-msg] Please send your feedback on 'whitespace' issue.


This could be serious for Intermediaries. When an IM adds an element to a signed message, it must be done without adding ANY whitespace. When an IM removes an element it must do so without deleting whitespace outside the element. <SOAP:Header...> <MessageHeader ...>... </MessageHeader> <ds:Signature>. . .</ds:Signature> </SOAP:Header> becomes: <SOAP:Header...> <MessageHeader ...>... </MessageHeader><SyncReply.../><AckRequested.../> <ds:Signature>. . .</ds:Signature> </SOAP:Header> Notice there is no whitespace (CRLF) added when adding the SyncReply and AckRequested. Is it reasonable to ask IMs to act like this? Should we show this in the spec? Sanjay's Transform, or something like it, might fix this problem so the IM could add elements on a new line as would be expected: <SOAP:Header...> <MessageHeader ...>... </MessageHeader> <ds:Signature>. . .</ds:Signature> <SyncReply.../> <AckRequested.../> </SOAP:Header> OTOH, We could fix this problem by putting SyncReply and AckRequested back in Via so IMs change a flag instead of adding elements. Since Via is not signed, the problem would go away. In any case, this needs to be addressed. Regards, David Fischer Drummond Group. P.S. Thanks to Sanjay for identifying this problem, and to Cliff for testing/proving this problem on signed messages.

[Date Prev]  |  [Thread Prev]  |  [Thread Next]  |  [Date Next]   —  [Date Index]  |  [Thread Index]  |  [Month Index]  |  [List Home]