[wsf-c-dev] [jira] Commented: (WSFPHP-372) charset header is included twice when receiving an mtom message from a MTOM enabled php service

[matthew mcaughan (JIRA)]

    [ https://wso2.org/jira/browse/WSFPHP-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24227#action_24227 ] 

matthew mcaughan commented on WSFPHP-372:
-----------------------------------------

Narrowing in on the issue. It appears to be in the file wsf_out_transport_info.c method wsf_http_out_transport_info_set_content_type method. This callback is neglecting to check if the charset parameter is already in the content_type string. By not having this check in place the callback is erroneously appending a second charset, which is the root cause of this bug. 

The axis2/c project suffered from the same bug.  The resolution there was to check for the presence of charset already in the content_type header. If present do not append an additional "charset=" + info_impl->encoding. 

The wsf code suffers from the same bug and can use the same resolution. Coding the fix now and will begin the process of fix verification. If all turns out well will post a patch with in depth instructions on how to re-create this problem.

Regards,

Matt McAughan





> charset header is included twice when receiving an mtom message from a MTOM enabled php service
> -----------------------------------------------------------------------------------------------
>
>                 Key: WSFPHP-372
>                 URL: https://wso2.org/jira/browse/WSFPHP-372
>             Project: WSO2 WSF/PHP
>          Issue Type: Bug
>         Environment: Any
>            Reporter: Nandika Jayawardana
>
> HTTP/1.1 200 OK
> Date: Tue, 27 Jan 2009 03:59:59 GMT
> Server: Apache/2.2.4 (Win32) PHP/5.2.6
> X-Powered-By: PHP/5.2.6
> Transfer-Encoding: chunked
> Content-Type: multipart/related; boundary=MIMEBoundary545ab05a-61c4-42db-bd21-2b697864014a; type="application/xop+xml"; start="<0.ebf2ac3d-492f-4b21-b8cc-38b73ae660c3 at apache.org>"; start-info="application/soap+xml"; charset="UTF-8";charset=UTF-83a0d--MIMEBoundary545ab05a-61c4-42db-bd21-2b697864014acontent-transfer-encoding: binarycontent-id: 
>    <0.ebf2ac3d-492f-4b21-b8cc-38b73ae660c3 at apache.org>content-type: application/xop+xml;charset=UTF-8;type="application/soap+xml";

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira