Issue #41 open

Use Content-Type header character set when proxying messages

andysc
created an issue

As per: https://getsatisfaction.com/adroitlogic/topics/invalid_encoding_name_cp1252_error_in_wssecuritymanager

UltraESB is proxying messages to the target service using the system-set character set / encoding value (either Java default or via the -Dfile.encoding system property).

When a client sends a HTTP request with a Content-Type header that specifies a different character set, e.g.:

Content-Type: text/xml;charset=ISO-8859-1

UltraESB should inspect the header and use the client-specified character set for transmission to the target service.

Otherwise, the client's Content-Type header is still forwarded to the target system, specifying a different character set to the actual payload and causing the target system to respond with errors.

Comments (2)

  1. Ruwan Linton

    Hi Andy,

    I agree, if we receive a charset with the Content-Type header we should preserve the same charset.

    Will get this fixed on the default branch.

    Ruwan

  2. Log in to comment