You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Valery Ushakov (JIRA)" <ji...@apache.org> on 2010/07/03 21:17:50 UTC

[jira] Commented: (AXIS2-4037) Content-ID must not contain unquoted colon characters

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

Valery Ushakov commented on AXIS2-4037:
---------------------------------------

As far as I can see WSCOMMONS-541 and r947499 are about UUID format.
This bug is for MIME header syntax, not UUID syntax.


> 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....@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