[ http://issues.apache.org/jira/browse/AXIS2C-461?page=comments#action_12458207 ] Eran Chinthaka commented on AXIS2C-461: ---------------------------------------
Hi, If there is no SOAPAction and if the body contains a SOAP 1.1 message, it is not always wrong, if you have enabled REST handling. Even though you have a SOAP message, you can not assume that this should be a SOAP request. For example, there can be a service, acting as a proxy to another Web service. When you access this service, using a normal web service call, you send a SOAP message which has another SOAP message in the body of the first SOAP message. Now what if, you gonna access the same service using REST. Then you get the above scenario. So I don't think this is a bug. Disclaimer : I am not that familiar with C code or Axis2/C. But I am commenting on this issue, on my little knowledge on REST and SOAP. > If SOAP Action is missing in SOAP 1.1 request, it is assumed to be a REST call > ------------------------------------------------------------------------------ > > Key: AXIS2C-461 > URL: http://issues.apache.org/jira/browse/AXIS2C-461 > Project: Axis2-C > Issue Type: Bug > Components: core/engine > Affects Versions: Current (Nightly) > Reporter: Samisa Abeysinghe > Priority: Critical > > If the SOAP action is missing and what we have in the request is a SOAP > request, it is wrong to assume it to be a REST request. > This error is there in SOAP 1.1 handling logic in > modules/core/transport/http/http_transport_utils.c -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
