Skip to Main Content
Integration


This is an IBM Automation portal for Integration 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 API Connect
Created by Guest
Created on Apr 14, 2020

API Connect fails with internal error (500) when Content-Type header is send twice

Some of our clients are receiving strange internal errors from API calls to APIC v5 and after quite a long investigation we realized error happens when they send HTTP header "Content-Type" twice.

Errors we see in the DataPower logs:
TypeError: contenttype.toLowerCase is not a function.

Could you please do one of the following:
- fix this so that APIC discards all but the first/last header?
- fix this so that sensible error message is shown in DataPower logs and error 400 is returned to the client?

Error is caused by faulty GatewayScript deployed to the DataPower APIM domain by APIM (local:///isp/policy/apim.custom.js).

Functions for checking if content type is JSON/XML are not checking the type of contenttype parameter. Functions check only if the parameter contains length greater than 0 (which is true for both string and array).

Idea priority High
RFE ID 141661
RFE URL
RFE Product IBM API Connect
  • Guest
    Reply
    |
    Sep 16, 2021

    This is fixed via APAR LI81512 and shipped in 5.0.8.9.