[ 
https://issues.apache.org/jira/browse/CXF-8051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henning Normann updated CXF-8051:
---------------------------------
    Description: 
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.

Updated error observation: The reference to the content

  was: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.


> 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.
> Updated error observation: The reference to the content



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to