[SM-503] servicemix-http provider should not add the inMessage content-type header to the response if a new content-type is generated (mime messages)

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0-M1, 3.0-M2, 3.0, 3.0.1
• Fix Version/s: 3.0
• Component/s: servicemix-http
• Patch Info: Patch Available
• Assignee: Guillaume Nodet
• Reporter: Renaud Bruyeron
• Created: 28/Jul/06 08:26
• Updated: 31/Jul/06 14:33
• Resolved: 31/Jul/06 14:33

Description

This is similar to SM-502 - the loop line 111 of ProviderProcessor in servicemix-http adds a Content-Type header from the in message if there was one. The content-type is regenerated by the soapWriter a few lines later and should override the first one. However both end up in the http request.

To see the bug, create 2 http:endpoints, one consumer and one provider, the latter being target of the former. Then submit a Soap With Attachment request into the consumer. The output is invalid because the first Content-Type header does not match the content (boundaries are wrong).

The patch attached removes the first header.