[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=24059#action_24059 ] 

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

Here is some information on how to produce this error. 

Client - Microsoft WSE 3.0 C# client,  MTOM

Service - WSF PHP WSServer, WSDL mode, MTOM

The client is posting a file and a list of attributes to the service. The service is uploading  and downloading files using PHP + CURL. The service returns any files and a list of attributes to the client. The response from the service contains two charset attributes. WSE then raises an exception adding them to a dictionary.

Example request:
Content-Type: multipart/related; type="application/xop+xml"; boundary=--MIMEBoundary633685670483431758; start="<0.633685670483431758 at example.org>"; start-info="text/xml; charset=utf-8"

Example response:
Content-Type: multipart/related; boundary=MIMEBoundarydc5b3cae-ebd0-1dd1-3486-000f1f89f3f2; type="application/xop+xml"; start="<0.dc5b3cf4-ebd0-1dd1-3487-000f1f89f3f2 at apache.org>"; start-info="text/xml"; charset="UTF-8";charset=utf-8

Notice charset appears twice in the Content-Type header. 

Please feel free to ask for any additional information to resolve.

> 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