HTTP response header contains content-type as charser: instead of charset=
--------------------------------------------------------------------------
Key: AXIS2C-1518
URL: https://issues.apache.org/jira/browse/AXIS2C-1518
Project: Axis2-C
Issue Type: Bug
Components: IIS module
Affects Versions: 1.5.0
Environment: Windows server 2003 and IIS 6.0
Reporter: Trigent
Fix For: Next Version
The axis2c v1.5.0 web service is configured using MS IIS 6.0 on windows server
2003 , the HTTP response header contains the content-type as "charser:".
The ORACLE SOA server is unable to parse the axis2c HTTP response header
because of content-type (charser:).
The ORACLE SOA server expects, HTTP header content-type as "charset=".
When analyzed the asix2c version 1.5.0 source code , we found the following
function is returning the content-type:
axis2_status_t AXIS2_CALL
axis2_iis_out_transport_info_set_content_type(
axis2_http_out_transport_info_t * info,
const axutil_env_t * env,
const axis2_char_t * content_type)
{
axis2_iis_out_transport_info_t *info_impl = NULL;
info_impl = AXIS2_INTF_TO_IMPL(info);
info_impl->content_type[0] = '\0';
if (info_impl->encoding)
{
sprintf(info_impl->content_type, "%s%s%s", content_type, ";charser:",
info_impl->encoding);
}
else
{
strcat(info_impl->content_type, content_type);
}
return AXIS2_SUCCESS;
}
The function "axis2_iis_out_transport_info_set_content_type" is available in
the file -
src-1.5.0\src\core\transport\http\server\IIS\axis2_iis_out_transport_info.c
The HTTP response header content-type needs to be corrected to resolve this
issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
