axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom Jordahl (JIRA)" <>
Subject [jira] Commented: (AXIS-2319) Bad parsing of content type header for multipart messages
Date Fri, 02 Dec 2005 07:17:31 GMT
    [ ] 

Tom Jordahl commented on AXIS-2319:

Since Axis is using a standard JavaMail jar file, the bug seems to be in that library.
Since we do not control these jar files, fixing this problem may be difficult.

For reference see section 5.1. "Syntax of the Content-Type Header Field" in RFC 2045 -

> Bad parsing of content type header for multipart messages
> ---------------------------------------------------------
>          Key: AXIS-2319
>          URL:
>      Project: Apache Axis
>         Type: Bug
>   Components: Basic Architecture
>     Versions: 1.1
>     Reporter: Mattias Norlander

> I am accessing axis (v1.1) web services from a php client.
> When trying to send messages with attachments, the server cannot process them.
> This is what I get:
> Error in parsing mime data stream:  null
> at
> org.apache.axis.attachments.MultiPartRelatedInputStream.<init>(
> After some debugging I figured out where the problem was. 
> The content type header sent from php looks like this:
> multipart/related; boundary="abc"; type=text/xml
> Axis (MultiPartRelatedInputStream class) will then pass this data to the constructor
> javax.mail.internet.ContentType. This constructor will then throw an exception. The
> workaround is to add double quotes around the "text/xml" part, like this:
> multipart/related; boundary="abc"; type="text/xml"
> ... and everything works fine. The problem is this cannot be done without altering the
actual PHP soap
> implementation. And also, as far as I can see, the quotes are not mandatory. If you look
at the examples
> from w3, they don't use them:
> So I would consider this a bug in axis.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message