axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Veithen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AXIS2-4037) Content-ID must not contain unquoted colon characters
Date Sun, 04 Jul 2010 09:04:53 GMT

    [ https://issues.apache.org/jira/browse/AXIS2-4037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12885010#action_12885010
] 

Andreas Veithen commented on AXIS2-4037:
----------------------------------------

See http://svn.apache.org/viewvc/webservices/commons/trunk/modules/axiom/modules/axiom-api/src/main/java/org/apache/axiom/om/OMOutputFormat.java?r1=883357&r2=947146&pathrev=947146

> Content-ID must not contain unquoted colon characters
> -----------------------------------------------------
>
>                 Key: AXIS2-4037
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4037
>             Project: Axis2
>          Issue Type: Bug
>    Affects Versions: 1.5.1, 1.5
>            Reporter: Valery Ushakov
>            Assignee: Andreas Veithen
>            Priority: Minor
>             Fix For: 1.6
>
>
> Asix2 generated MTOM messages use content ids of the form
>   cid:1.urn:uuid:696D3CB9D9461274431221754142198@apache.org
> when that content id is manifested in a MIME multipart message the resulting headers
is
>   Content-ID <1.urn:uuid:696D3CB9D9461274431221754142198@apache.org>
> but that header violates RFC syntax for Content-ID.
> RFC2045 (MIME, Part 1) defines Content-ID as
>   "Content-ID" ":" msg-id
> RFC2822 defines msg-id as
>   msg-id          =       [CFWS] "<" id-left "@" id-right ">" [CFWS]
> where no unquoted variant of if-left can NOT contain colon character (see RFC2822 for
details and exact productions).
> This is an interoperability problem for systems that try to parse Axis2 generated messages
using MIME parsers that are not happy about those illegal colons.
> Note that I'm not using axis2 myself, so unfortunately I cannot provide any further details,
but it looks like axis2 has always been generating such content-ids.  I'm filing this to find
out if this is indeed a bug in axis2 or if I'm misreading relevant standards and I need to
fix the MIME parser I use.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


Mime
View raw message