cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gina Choi <ginacho...@gmail.com>
Subject Fediz STS - A SOAP 1.2 message is not valid when sent to a SOAP 1.1 only endpoint
Date Mon, 16 Jul 2012 11:35:31 GMT
Hi All,

One of my colleage sent a SOAP1.2 RST to Fediz STS UTEncrypted end point
from his .NET client and he received back following response. He changed
format to SOAP1.1 to get by this error message, but he really need to run
with SOAP1.2. Is there anywhere to enable SOAP1.2 message in STS to accept
1.2 format?


<MessageLogTraceRecord>

<HttpResponse xmlns="*
http://schemas.microsoft.com/2004/06/ServiceModel/Management/MessageTrace*">

<StatusCode>*InternalServerError*</StatusCode>

<StatusDescription>*Internal Server Error*</StatusDescription>

<WebHeaders>

<Transfer-Encoding>*chunked*</Transfer-Encoding>

<Connection>*close*</Connection>

<Content-Type>*application/soap+xml;charset=UTF-8*</Content-Type>

<Date>*Wed, 11 Jul 2012 12:34:20 GMT*</Date>

<Server>*Apache-Coyote/1.1*</Server>

</WebHeaders>

</HttpResponse>

<soap:Envelope xmlns:soap="*http://www.w3.org/2003/05/soap-envelope*">

<s:Header xmlns:s="*http://www.w3.org/2003/05/soap-envelope*"></s:Header>

<soap:Body>

<soap:Fault>

<faultcode xmlns:ns1="*http://schemas.xmlsoap.org/soap/envelope/*" xmlns="">
*ns1:VersionMismatch*</faultcode>

<faultstring xmlns="">*A SOAP 1.2 message is not valid when sent to a SOAP
1.1 only endpoint.*</faultstring>

</soap:Fault>

</soap:Body>

</soap:Envelope>

</MessageLogTraceRecord>


Thanks.

Gina

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message