You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Renaud Bruyeron (JIRA)" <ji...@apache.org> on 2006/07/28 10:26:23 UTC
[jira] Created: (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)
servicemix-http provider should not add the inMessage content-type header to the response if a new content-type is generated (mime messages)
--------------------------------------------------------------------------------------------------------------------------------------------
Key: SM-503
URL: https://issues.apache.org/activemq/browse/SM-503
Project: ServiceMix
Issue Type: Bug
Components: servicemix-http
Affects Versions: 3.0-M1, 3.0-M2, 3.0-M3, 3.0
Reporter: Renaud Bruyeron
Fix For: 3.0
Attachments: patch.txt
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (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)
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/SM-503?page=all ]
Guillaume Nodet resolved SM-503.
--------------------------------
Fix Version/s: 3.0-M3
(was: 3.0)
Resolution: Fixed
Assignee: Guillaume Nodet
Author: gnodet
Date: Mon Jul 31 07:34:49 2006
New Revision: 427129
URL: http://svn.apache.org/viewvc?rev=427129&view=rev
Log:
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)
Patch provided by Renaud Bruyeron, thx !
Modified:
incubator/servicemix/trunk/servicemix-http/src/main/java/org/apache/servicemix/http/processors/ConsumerProcessor.java
incubator/servicemix/trunk/servicemix-http/src/main/java/org/apache/servicemix/http/processors/ProviderProcessor.java
incubator/servicemix/trunk/servicemix-http/src/test/java/org/apache/servicemix/http/HttpSoapTest.java
> servicemix-http provider should not add the inMessage content-type header to the response if a new content-type is generated (mime messages)
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SM-503
> URL: https://issues.apache.org/activemq/browse/SM-503
> Project: ServiceMix
> Issue Type: Bug
> Components: servicemix-http
> Affects Versions: 3.0-M1, 3.0-M2, 3.0-M3, 3.0
> Reporter: Renaud Bruyeron
> Assigned To: Guillaume Nodet
> Fix For: 3.0-M3
>
> Attachments: patch.txt
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira