Hi Folks,
It appears that the Synapse NHTTP transport is not properly handling the
response messages that don't have a Content-Type header. Currently when the
Content-Type header is not present in a response message the following bit
of code is executed by the ClientWorker.
// the
Hiranya,
Lets make it a bit more flexible and make it configurable.
We can have a axis2.xml parameter to specify the default content-type if
there is no content type in the response. Also it should be possible to
overwrite the axis2.xml parameter from the message context as well.
So ideally when
On Thu, Oct 1, 2009 at 12:32 PM, Ruwan Linton wrote:
> Hiranya,
>
> Lets make it a bit more flexible and make it configurable.
>
> We can have a axis2.xml parameter to specify the default content-type if
> there is no content type in the response. Also it should be possible to
> overwrite the axis
On Thu, Oct 1, 2009 at 1:09 PM, Hiranya Jayathilaka wrote:
>
>
> On Thu, Oct 1, 2009 at 12:32 PM, Ruwan Linton wrote:
>
>> Hiranya,
>>
>> Lets make it a bit more flexible and make it configurable.
>>
>> We can have a axis2.xml parameter to specify the default content-type if
>> there is no content