[
https://issues.apache.org/jira/browse/CXF-8051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16863232#comment-16863232
]
Colm O hEigeartaigh commented on CXF-8051:
------------------------------------------
You could try writing a custom interceptor to override the Cookie xop:Include
value with the correct value from the attachment. I'm not sure this is
something CXF should handle out of the box, as the Cookie Element is something
specific to Microsoft and not a standard value.
> 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: Debugging the service (ref attached payload
> EcBad.txt) shows that the problem is that the reference in the xop element in
> the security token cookie doesn’t match the content id for the binary payload:
> <xop:Include xmlns:xop="http://www.w3.org/2004/08/xop/include";
> href=[cid:http://tempuri.org/1/636951518227439376]
> Content-ID:
> [[email protected]|mailto:[email protected]]
> It’s expected that the content id should match the value after cid int the
> xop href. (At least that works for consumers written with other technologies
> than CXF.)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
