[jira] Commented: (AXIS2C-1254) Information set by the Client options axis2_options_set_transport_info function is not used

[ https://issues.apache.org/jira/browse/AXIS2C-1254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12626893#action_12626893 ] Damitha Kumarage commented on AXIS2C-1254: -- I had a look at your patch. Is not it

Re: Service client options to set custom HTTP headers

Hi Danushka, override options come into play when we reuse operation client. Say after sending some application messages you need to override some options. Then you create new options struct and called svc client's set_override_options. What happens is that existing options struct becomes

[jira] Commented: (AXIS2C-1254) Information set by the Client options axis2_options_set_transport_info function is not used

[ https://issues.apache.org/jira/browse/AXIS2C-1254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12626897#action_12626897 ] Supun Kamburugamuva commented on AXIS2C-1254: - I think if a client

Re: Service client options to set custom HTTP headers

override options come into play when we reuse operation client. Say after sending some application messages you need to override some options. Then you create new options struct and called svc client's set_override_options. What happens is that existing options struct becomes parent and your

Re: Service client options to set custom HTTP headers

Danushka Menikkumbura wrote: Hi Devs, There is a requirement to have support for custom HTTP headers in Axis2/C. To do that we need to let the operation client know the header details. One options is to set headers in service client options and pass them on to operation client as the

Re: Service client options to set custom HTTP headers

So what is the option that you propose? HTTP_HEADERS = array of (key = value) ? An array of axis2_http_header_t*. Danushka -- Danushka Menikkumbura Technical Lead, WSO2 Inc. blog : http://danushka-menikkumbura.blogspot.com/ http://wso2.com/ - The Open Source SOA Company

Re: Service client options to set custom HTTP headers

Danushka Menikkumbura wrote: So what is the option that you propose? HTTP_HEADERS = array of (key = value) ? An array of axis2_http_header_t*. But then the user need to create axis2_http_header_t instances. Can we use an string key value pair and covert them to the header type internally?

Re: Service client options to set custom HTTP headers

But then the user need to create axis2_http_header_t instances. Can we use an string key value pair and covert them to the header type internally? No he doesn't have to. The interface call accepts the name and the value and it in turn creates the header instance. The interface call :