Skip to Main Content
Cloud Platform

This is an IBM Automation portal for Cloud Platform products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Workspace WebSphere Liberty
Created by Guest
Created on Feb 6, 2019

Rest service doesn't give back information on CHARSET

When I consume a REST service I don't receive any information in HTTP header about CHARSET . Due to this the instruments that I use ( HTTP call from RPGILE, SQL, SOAP call , etc.) are not able to understand which set of character use, so particular letter in my alphabet (for example É) are not resolved in the correct way, but using a default is treated like how separate different hex values. So for É I give É. The actual solutions provided by software assistance it's force that charset value in the conf file of the server. In my case : Header always set Content-Type: "application/xml; charset=UTF-8" "expr=%{REQUEST_URI} =~ m#^/web/services/fattel/(.*)$#" . But this for me shouldn't be a solution for any other wss that I need to develop. So what I need it's to have the possibility to set somewhere during the deploy of a new web service that value. Or at least to set a default, but not changing directly the conf file. The software assistance refer to me that this is related to Liberty Server, more than Application Server itself.

Idea priority High
RFE ID 129729
RFE Product WebSphere Application Server
  • Guest
    Nov 15, 2021

    Thank you for responding. We were trying to make sure that we understood the request correctly. It sounds like it was a good thing we did because we thought you were asking for something different from what you are asking. The request is now clear to us so I'm moving it back to the Under Review state so we will rereview during our next screening discussion.

  • Guest
    Nov 15, 2021

    Not sure why you think it should be a configuration option. What I am asking for is the jax-rs engine recognize the encoding set for the JVM and map that to a charset that MUST be set in the response in order to support National Language Versions. Otherwise, with no CHARSET specified, the default in HTTP is ISO-8859-1.

    So if the CHARSET is not specified by web service, the JAX-RS engine would set it accordingly.

    This should be done transparently - no configuration option. For example, in JVM with


    The JAX-RS engine would map to charset=UTF-8.

    For JAX-WS, charset is always set by the JAX-WS engine. Only asking for the logical thing to do in JAX-RS. Otherwise, burden on web services to ensure the charset is set.

  • Guest
    Nov 5, 2021

    Posted on behalf of our JAX-RS SME

    If I understand correctly, it sounds like you are asking for two things: (1) That Liberty's JAX-RS responses should always include the charset attribute in the Content-type header. Perhaps this could be a configuration option.

    (2) That users could configure the actual charset used in the JAX-RS response. So if the default is UTF-8, then it would be possible for the user to configure one application to use UTF-16, and another to use UTF-32 (for example). Is that correct? I'm a little confused about the comment regarding where to make the configuration change. Would it not be appropriate to add the configuration switches into the Liberty configuration (server.xml)?

    Thanks in advance for the clarification,


  • Guest
    Feb 6, 2019

    Just to clarify, SOAP responses using JAX-WS included the charset, for example:

    Content-Type: text/xml; charset=UTF-8

    However, when using JAX-RS where a simple POJO with annotations controlling whether to return XML or JSON, the Content-Type header does not include a charset:

    Content-Type: application/xml

    And again, this is running on the IBM Liberty server.