[ http://issues.apache.org/jira/browse/AXIS2-209?page=comments#action_12322806 ]
Eran Chinthaka commented on AXIS2-209: -------------------------------------- Well, I fixed this with a simple URLDecoder, but gives rise to another question for me. We have other URIs every where in the recd SOAP message. How do we treat them, if they are encoded too. Are we leaving that out to the user or do we need to decode ALL of them. I don't like the latter option, since I doubt that will degrade the performance. How do you all feel about this ? (I'm not marking this as fixed due to the above concern I raised. But what the initial issue addresses has been fixed now) > 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
