[
https://issues.apache.org/jira/browse/AXIS2-4037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884961#action_12884961
]
Andreas Veithen commented on AXIS2-4037:
----------------------------------------
@Valery: from AXIS2-4527: "my suggestion is to revert r939925, deprecate the
whole UUIDGenerator stuff and replace it by a new, well defined utility class
that is able to produce unique/random identifiers of various kinds (UUIDs, MIME
content IDs, MIME boundaries) that respect the relevant standards"
> 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:[email protected]
> when that content id is manifested in a MIME multipart message the resulting
> headers is
> Content-ID <1.urn:uuid:[email protected]>
> 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: [email protected]
For additional commands, e-mail: [email protected]
