[ http://issues.apache.org/jira/browse/AXIS2-209?page=comments#action_12322901 ]
Dennis Sosnoski commented on AXIS2-209: --------------------------------------- Great references, Sanjiva, and I'd agree with your conclusion except that in this example the scheme is "cid". If I read http://www.ietf.org/rfc/rfc2111.txt correctly, it looks like the value of a cid: reference should properly be URL encoded, since it's being used as basically an opaque token. In particular, this seems to say that '/' *has* to be escaped, unless it's being used for the special purpose defined by mid: references. So it looks to me that the unencoding needs to be done, at least for this particular use of URIs (and the encoding has to be done, when generating URIs of this type). > mtom cid with encoded url > ------------------------- > > Key: AXIS2-209 > URL: http://issues.apache.org/jira/browse/AXIS2-209 > Project: Apache Axis 2.0 (Axis2) > Type: Bug > Reporter: Davanum Srinivas > Assignee: Saminda Wishwajith Abeyruwan > > Indigo is sending a xop include like this > <xop:Include href="cid:http%3A%2F%2Ftempuri.org%2F2%2F632616398833933905" > xmlns:xop="http://www.w3.org/2004/08/xop/include"/> > with a content-id like this > --uuid:f83d35ae-9bf5-470a-8fb4-7b624abd6921+id=1 > Content-ID: <http://tempuri.org/2/632616398833933905> > Content-Transfer-Encoding: binary > Content-Type: application/octet-stream > This "seems" to be legal. can someone please dig into this? > thanks, > dims -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
