[
http://issues.apache.org/jira/browse/AXIS2-802?page=comments#action_12422619 ]
Eran Chinthaka commented on AXIS2-802:
--
Seems the issue is fixed once user sets the correct content type
> Possible header formation bug
>
[
http://issues.apache.org/jira/browse/AXIS2-802?page=comments#action_12422618 ]
Eran Chinthaka commented on AXIS2-802:
--
Seems the issue is fixed once user sets the current content type
> Possible header formation bug
>
[
http://issues.apache.org/jira/browse/AXIS2-802?page=comments#action_12422615 ]
Eran Chinthaka commented on AXIS2-802:
--
s/current/correct
> Possible header formation bug
> -
>
> Key: AXIS2-802
>
[
http://issues.apache.org/jira/browse/AXIS2-802?page=comments#action_12421813 ]
Matthias Göttler commented on AXIS2-802:
Maybe not really fitting to the situation explained in the original
description, but we experienced the named excep
[
http://issues.apache.org/jira/browse/AXIS2-802?page=comments#action_12415932 ]
Davanum Srinivas commented on AXIS2-802:
Can u please post the whole stack trace? may be a test case for us to recreate
the problem as well? Alternatively, please try t
