axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis Sosnoski (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AXIS2-209) mtom cid with encoded url
Date Wed, 07 Sep 2005 06:01:30 GMT
    [ http://issues.apache.org/jira/browse/AXIS2-209?page=comments#action_12322805 ] 

Dennis Sosnoski commented on AXIS2-209:
---------------------------------------

Whoops, ignore that last comment. The URL escaping would not be handled by the parser at all,
since it doesn't know the attribute is of an anyURI type. Looks like the unescaping has to
be handled by the Axis2 code that interprets this as an XOP include.

> 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


Mime
View raw message