Archived Forum Post

Index of archived forum posts

Question:

possible soap version mismatch

Jan 18 '16 at 15:00

I'm working on my first Chilkat/HTTP/SOAP project and I can't get past this error. From what I've found online, it seems to be caused by version 1.1 vs 1.2 and can be fixed by setting the SOAP namespace to "http://schemas.xmlsoap.org/soap/envelope/". But I can't figure out how to create or set a property to force v1.1. I hope this makes sense; I'm not even sure I can ask the question intelligently at this point.

<soap:envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <soap:header> <soap12:upgrade xmlns:soap12="http://www.w3.org/2003/05/soap-envelope"> <soap12:supportedenvelope qname="soap:Envelope" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"/> <soap12:supportedenvelope qname="soap12:Envelope" xmlns:soap12="http://www.w3.org/2003/05/soap-envelope"/> </soap12:upgrade> </soap:header> <soap:body> <soap:fault> <faultcode>soap:VersionMismatch</faultcode> <faultstring>Possible SOAP version mismatch: Envelope namespace was unexpected. Expecting http://schemas.xmlsoap.org/soap/envelope/.</faultstring> <detail/> </soap:fault> </soap:body> </soap:envelope>

---

Answer

Chilkat HTTP is not building the SOAP XML for you -- it is your application code that builds the SOAP XML. The solution is to change whatever application code is building the SOAP XML to use whatever it is you need.

---

Answer

Thanks, I wasn't sure what was being done where. I think I'm on the right track now.