[
https://issues.apache.org/jira/browse/CXF-8051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16880788#comment-16880788
]
Henning Normann commented on CXF-8051:
--------------------------------------
Now it works😊 I would expect the token payload to be MTOM for an MTOM service,
but it doesn’t matter to us whether it’s inline base64 or MTOM. When do you
think that the PR will be merged, and is there a target date for 3.3.3?
> 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
> Assignee: Colm O hEigeartaigh
> Priority: Major
> Attachments: EcBad.txt, EcGood.txt,
> ResponseFromSecurityTokenService.txt
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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 2nd time: When the request is streamed, CXF doesn't stream the
> payload of the content of the token cookie, and the reference from the cookie
> is "unresolved". When the request is not-streamed, the cookie payload is
> included as base64 inside the cookie element, and everything works fine. The
> attached formatted requests EcBad.txt (failing from CXF) and EcGood.txt
> (valid request from a .NET WCF client) show the issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
