[ http://issues.apache.org/jira/browse/AXIS2-209?page=all ] Davanum Srinivas reopened AXIS2-209: ------------------------------------
Reopening issue as per Thilina on mailing list: Ahh... My bad... I didn't notice the Jira before to comment on it.. BTW this problem is still there when it comes to UTF-16. WCF sends a URL encoded content-id and Axis2 cannot figure it out. IMO the problem may be with our stax parser not being able to handle UTF-16 URL encoded strings.. This issue caused one UTF-16 test to fail in the MTOM interop testing with WCF... WCF people will try to remove the URL encoding since it's not required at that point (MTOM-Cid).. Even if they removed it we need to look in to the problem, since this might give troubles in other UTF-16 cases... ~Thilina > 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
