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 Delivered
Workspace z/OS Connect
Created by Guest
Created on Mar 25, 2020

ARInvokeHandler sets the Accept to always be MediaType.APPLICATION_JSON this needs to be configurable

An external API provider uses the Accept/Content headers for versioning.

We have set the zconbt property ignoreMIMETypeCheck=true which allows the ARA build to complete. However when driving the API requester we get a 406 response as zOS Connect sets the value back to application/json rather than the value required by the API provider who rejects the request.

So there seems to be a mismatch in support for custom MIME type headers in that the toolkit will at least ignore them so processing can continue however the API Requester code just sets the default application/json value.

Idea priority Urgent
  • Guest
    Reply
    |
    Mar 22, 2021

    This requirement is addressed by z/OS Connect Enterprise Edition V3.0.43 / APAR PH34379:
    https://www.ibm.com/support/pages/apar/PH34379

    The he optional attributes: ignoreMIMETypeCheck and useMIMEType, can be use in the build toolkit properties file to handle custom MIME types for API Requesters.

    For further details about MIME Type handling for API requester, refer to the “The build toolkit properties file” topic in the z/OS Connect EE V3.0 Knowledge Center:
    https://www.ibm.com/support/knowledgecenter/SS4SVW_3.0.0/facilitating/build_toolkit_prop.html