axis-java-dev mailing list archives

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

Sanjiva Weerawarana commented on AXIS2-209:
-------------------------------------------

Indigo is incorrect AFAICT.

See: http://www.w3.org/2001/tag/issues.html and look at issue URIEquivalence-15. 
See: http://www.textuality.com/tag/uri-comp-4
See RFC 2396bis: http://cvs.apache.org/viewcvs.cgi/*checkout*/ietf-uri/rev-2002/rfc2396bis.html
See RFC 3986: http://www.faqs.org/rfcs/rfc3986.html

In particular the issue is that the ":" separating the scheme and the rest in URI is very
special, as is the "/" character. The above specs appear to say that the ":" cannot be URL
encoded and that the path separators ("/") shouldn't be. 

If you read some of the above (I only did a quick review now ..) you'll see that at best what
Indigo is doing is inconsistent with suggested best practice.

Let's get them to change it; messing with normalizing URIs strings before comparing them is
a very *bad* idea IMO.

> 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