Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software 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 (https://ideas.ibm.com).


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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Categories Runtime
Created by Guest
Created on Oct 20, 2016

Support additional Content-Types as textual in WEB CONVERSE

When WEB CONVERSE receives a response and places it in a container, it uses the Content-Type header to determine whether to create a BIT or CHAR container for the response. e.g. Well-known Content-Types such as 'application/json' result in a CHAR container.

However, other standard Content-Types such as 'application/vnd.api+json' result in a BIT container, even though the Content-Type indicates that the response is JSON and therefore in textual format.

Please extend the determination based on Content-Type to be sensitive to the standard IANA suffix '+json' (as per '+xml'), and treat the response as text.

Ref: https://tools.ietf.org/html/rfc6839#section-3.1
"The suffix '+json' MAY be used with any media type whose representation follows that established for 'application/json'."

Per discussion with Mark Cocker, Oct 2016 in Melbourne, Australia.

Idea priority Medium
  • Guest
    Reply
    |
    Mar 2, 2021

    This requirements has been re-assessed. We have no plans for this to be implemented and so this requirement is being declined at this point. The requirement will be kept in the RFE system and might be reassessed in the future. You also have an opportunity to resubmit in twelve months time if you wish it to be reconsidered then.