[progress Communities] [progress Openedge Abl] Forum Post: Support Soap 1.2 On Server Side

  • Thread starter Thread starter Valeriy Bashkatov
  • Start date Start date
Status
Not open for further replies.
V

Valeriy Bashkatov

Guest
Hello, OS: Windows 32-bit OpenEdge 11.3.0 Web Service Adapter was created using OpenEdge Explorer and Apache Tomcat 8. Earlier, during the POST request to the WSA, the third party client passed in the header field SOAPAction = "". And it worked well. But now the third party client this field does not pass and WSA refuses to service the request, issuing an error: "HTTP request denied (400): The HTTP request was missing the SOAPAction header (10954)". The third party client now use SOAP 1.2 standart where this field (SOAPAction) is not mandatory. And we can not to change it in any way. In the ProKB http://knowledgebase.progress.com/articles/Article/P125350 says that OpenEdge 11.3 and later support both the SOAP 1.1 and SOAP 1.2 standards. But how to implement it (SOAP 1.2)? Customer's Web services created using ProxyGenerator and published through OpenEdge Explorer. Neither is any other place I have not found a setting to select SOAP 1.2 as standard. Does anyone know how to solve this problem? Regards, Valeriy

Continue reading...
 
Status
Not open for further replies.
Back
Top