synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Heshan Suriyaarachchi (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (SYNAPSE-662) ClientWorker overriding character encoding
Date Thu, 15 Jul 2010 04:45:50 GMT

    [ https://issues.apache.org/jira/browse/SYNAPSE-662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12888696#action_12888696
] 

Heshan Suriyaarachchi edited comment on SYNAPSE-662 at 7/15/10 12:44 AM:
-------------------------------------------------------------------------

Hi Myles,
             Do you use UTF-16 encoding with Synapse-1.2 or have you used UTF-16 to prove
your point?

      was (Author: heshan):
    Hi Myles,
             Do you use UTF-16 encoding with Synapse-1.2 or have you used UTF-16 to prove
your point?

  
> ClientWorker overriding character encoding
> ------------------------------------------
>
>                 Key: SYNAPSE-662
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-662
>             Project: Synapse
>          Issue Type: Bug
>    Affects Versions: 1.2
>            Reporter: Myles Bunbury
>         Attachments: SYNAPSE-662-patch.txt
>
>
> The following code exists in the org.apache.synapse.transport.nhttp.ClientWorker class'
run() method:
>                 responseMsgCtx.setProperty(
>                     Constants.Configuration.CHARACTER_SET_ENCODING,
>                     contentType.indexOf(HTTP.CHARSET_PARAM) > 0 ?
>                         charSetEnc : MessageContext.DEFAULT_CHAR_SET_ENCODING);
> This fails however for the following Content-Type HTTP header:
>   application/soap+xml; action="urn:echoResponse";charset=UTF-16
> BuilderUtil.getCharSetEncoding(contentType) is called a few lines up and correctly extracts
the UTF-16 character set value, but then overrides this and sets it to UTF-8. It does this
because the value of org.apache.http.protocol.HTTP.CHARSET_PARAM is "; charset=". That is,
it's failing because the response does not have a space between the charset parameter and
the previous parameter.
> Reading through the HTTP specs, I haven't come across anything that says either that
whitespace is permissible or not permissible here. In my view the code should therfore be
flexible enough to handle either case. 
> I would suggest simpifying the code to:
>      responseMsgCtx.setProperty(Constants.Configuration.CHARACTER_SET_ENCODING, charSetEnc);
> as the BuilderUtil.getCharSetEncoding() code above the offending code seems to be sufficient
at first glance.

-- 
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org


Mime
View raw message