[
https://issues.apache.org/jira/browse/CXF-8051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16851863#comment-16851863
]
Henning Normann commented on CXF-8051:
--------------------------------------
I thought that WS-Security was mandatory for a secure conversation and a
stateful security token. The service works fine from CXF with streamed secure
conversation with stateless security token. It also works fine for both
stateful and stateless security tokens when the service is none-streamed. It
also works for other bindings.
> Request gets corrupted when calling a stateful streamed secure conversation
> ---------------------------------------------------------------------------
>
> Key: CXF-8051
> URL: https://issues.apache.org/jira/browse/CXF-8051
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
> Affects Versions: 3.3.2
> Environment: The request is running in a console application hosted
> in Netbeans on Windows Server 2012 R2. The service is a .NET WCF service on
> Windows Server 2012 R2.
> Reporter: Henning Normann
> Priority: Major
> Attachments: EcBad.txt, EcGood.txt
>
>
> The request to a streamed secure conversation web service gets corrupted if
> the service (.NET WCF) is configured as stateless (with a stateful token
> carrying the state in soap cookies). If the service as configured as stateful
> (no soap cookies), the request is valid. When it's corrupted, a tree digit
> number is inserted in the Content-Transfer-Encoding header. A corrupt (search
> for 632) and a valid request are attached. The requests were recorded by
> Wireshark on the service host server.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
