You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Thomas Termin (JIRA)" <ji...@apache.org> on 2011/01/21 18:56:43 UTC
[jira] Created: (SMXCOMP-845) http provider processor - simple
response content type check missing which can lead to errors.
http provider processor - simple response content type check missing which can lead to errors.
----------------------------------------------------------------------------------------------
Key: SMXCOMP-845
URL: https://issues.apache.org/jira/browse/SMXCOMP-845
Project: ServiceMix Components
Issue Type: Bug
Components: servicemix-http
Affects Versions: 2010.02
Reporter: Thomas Termin
Assignee: Thomas Termin
Fix For: 2011.01
If an request is sended via the provider the http server can respond with non xml documents like http errors are. What happens is that the response is set as fault. The next component parsing the exchange fault content get's an error because the xml is not valid. There should be at least a small check if the content type contains the word "xml". If not an exception should be thrown which results to an error in the logfile and an exchange status error.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Work started: (SMXCOMP-845) http provider processor - simple
response content type check missing which can lead to errors.
Posted by "Thomas Termin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SMXCOMP-845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on SMXCOMP-845 started by Thomas Termin.
> http provider processor - simple response content type check missing which can lead to errors.
> ----------------------------------------------------------------------------------------------
>
> Key: SMXCOMP-845
> URL: https://issues.apache.org/jira/browse/SMXCOMP-845
> Project: ServiceMix Components
> Issue Type: Bug
> Components: servicemix-http
> Affects Versions: 2010.02
> Reporter: Thomas Termin
> Assignee: Thomas Termin
> Fix For: 2011.01
>
>
> If an request is sended via the provider the http server can respond with non xml documents like http errors are. What happens is that the response is set as fault. The next component parsing the exchange fault content get's an error because the xml is not valid. There should be at least a small check if the content type contains the word "xml". If not an exception should be thrown which results to an error in the logfile and an exchange status error.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SMXCOMP-845) http provider processor - simple
response content type check missing which can lead to errors.
Posted by "Thomas Termin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SMXCOMP-845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Termin resolved SMXCOMP-845.
-----------------------------------
Resolution: Fixed
Author: tterm
Date: Wed Jan 26 13:52:02 2011
New Revision: 1063719
URL: http://svn.apache.org/viewvc?rev=1063719&view=rev
Log:
SMXCOMP-845 http provider processor - simple response content type check missing which can lead to errors.
Modified:
servicemix/components/trunk/bindings/servicemix-http/src/main/java/org/apache/servicemix/http/HttpEndpoint.java
servicemix/components/trunk/bindings/servicemix-http/src/main/java/org/apache/servicemix/http/processors/ProviderProcessor.java
> http provider processor - simple response content type check missing which can lead to errors.
> ----------------------------------------------------------------------------------------------
>
> Key: SMXCOMP-845
> URL: https://issues.apache.org/jira/browse/SMXCOMP-845
> Project: ServiceMix Components
> Issue Type: Bug
> Components: servicemix-http
> Affects Versions: 2010.02
> Reporter: Thomas Termin
> Assignee: Thomas Termin
> Fix For: 2011.01
>
>
> If an request is sended via the provider the http server can respond with non xml documents like http errors are. What happens is that the response is set as fault. The next component parsing the exchange fault content get's an error because the xml is not valid. There should be at least a small check if the content type contains the word "xml". If not an exception should be thrown which results to an error in the logfile and an exchange status error.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.