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 Future consideration
Workspace z/OS Connect
Created by Guest
Created on Nov 30, 2021

Setting a custom value for the Content-Type HTTP header in z/OS Connect API response messages

We are currently trying to align the error messages sent by our company's REST APIs with this RFC: https://datatracker.ietf.org/doc/html/rfc7807 (Problem Details for HTTP APIs).

One of the standards in the RFC is setting the Content-Type HTTP header to application/problem+json for error messages, instead of application/json which is the only possibility for z/OS Connect API response messages.

So in order to conform to this RFC, we require to set a custom value for the Content-Type HTTP header in z/OS Connect response messages.

Regards,
Thomas Parmentier

Idea priority Low