This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(96, 28.999999999999996%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAS%3C/text%3E%3C/svg%3E)
i'have tried this but MustUnderstand is still equal to 1.
Do i need to set a callback to my WS_PROXY_MESSAGE_CALLBACK_CONTEXT mustUnderstand ? If yes, which callback ?
WS_CALL_PROPERTY callProperties[1];
WS_PROXY_MESSAGE_CALLBACK_CONTEXT mustUnderstand= {0};
BOOL mustU = FALSE;
mustUnderstand.state = &mustU;
callProperties[0].id = WS_CALL_PROPERTY_SEND_MESSAGE_CONTEXT;
callProperties[0].value = &mustUnderstand;
callProperties[0].valueSize = 4;
WsCall...
WS_CALL_PROPERTY_CHECK_MUST_UNDERSTAND=0: An application can suppress or enable must understand header processing on the proxy using this setting. This is TRUE by default.
WS_CALL_PROPERTY_SEND_MESSAGE_CONTEXT=1: Enables an application to put headers into the input message for a given call.
Whether you want to suppress must understand header processing on the proxy? If so, as far as I'm concerned, you should use WS_CALL_PROPERTY_CHECK_MUST_UNDERSTAND instead of WS_CALL_PROPERTY_SEND_MESSAGE_CONTEXT.
Sorry i've made a mistake, in my example :
WS_CALL_PROPERTY callProperties[1];
WS_PROXY_MESSAGE_CALLBACK_CONTEXT mustUnderstand= {0};
BOOL mustU = FALSE;
mustUnderstand.state = &mustU;
callProperties[0].id = WS_CALL_PROPERTY_CHECK_MUST_UNDERSTAND ;
callProperties[0].value = &mustUnderstand;
callProperties[0].valueSize = 4;
WsCall..
But it didn't work. I guess it is maybe because of the callback ? Can you help me ?
According to the Doc: WS_CALL_PROPERTY_ID enumeration
WS_CALL_PROPERTY_CHECK_MUST_UNDERSTAND: This is TRUE by default.
WS_PROXY_MESSAGE_CALLBACK_CONTEXT structure: Specifies the callback function and state for an application that wishes to associate or inspect headers in an input or an output message respectively.
As far as I'm concerned, you could set WS_CALL_PROPERTY_SEND_MESSAGE_CONTEXT and
WS_CALL_PROPERTY_RECEIVE_MESSAGE_CONTEXT in WS_PROXY_MESSAGE_CALLBACK_CONTEXT.
Sorry but i did not understand your suggestion.
Here is my code, in the callback value, if i need it, i have to set a function.
WS_CALL_PROPERTY callProperties[2];
WS_PROXY_MESSAGE_CALLBACK_CONTEXT inputMessageContext= {0};
inputMessageContext.callback = AddCustomHeader;
inputMessageContext.state= &infos;
callProperties[0].id = WS_CALL_PROPERTY_SEND_MESSAGE_CONTEXT ;
callProperties[0].value = &inputMessageContext;
callProperties[0].valueSize = sizeof(inputMessageContext);
WS_PROXY_MESSAGE_CALLBACK_CONTEXT mustUnderstandContext= {0};
BOOL mustU = FALSE;
mustUnderstandContext.state = &mustU;
mustUnderstandContext.callback = NULL;
callProperties[1].id = WS_CALL_PROPERTY_CHECK_MUST_UNDERSTAND ;
callProperties[1].value = &mustUnderstandContext;
callProperties[1].valueSize = 4;
The part with WS_CALL_PROPERTY_SEND_MESSAGE_CONTEXT works well but now i work on the WS_CALL_PROPERTY_CHECK_MUST_UNDERSTAND part
If you want to use WS_CALL_PROPERTY_CHECK_MUST_UNDERSTAND, in my opinion, you should use WS_CALL_PROPERTY structure instead of WS_PROXY_MESSAGE_CALLBACK_CONTEXT structure.
Ok thank you for the help
I 've found another way : change the WS_CHANNEL_PROPERTY_ADDRESSING_VERSION not to have "must understand" things