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 Future consideration
Workspace App Connect
Created by Guest
Created on Dec 22, 2021

HTTP Request Node to support Expect:100-continue header

Hello Team,


We are developed simple message flow which invoke the api using HTTP request node and mentioned the Expect field with the value 100-continue on HTTPRequestHeader folder. Then I expect an outgoing request to ask the server to first acknowledge that everything is fine (response code informational 100) and that it can continue to send the “payload” – or it can return status codes that informs the client that there are other things it needs to fulfil in order to have the request succeed.

However the message flow that we developed seem not behave as expected. Therefore please can this feature incorporated into App Connect Enterprise



Actual:

IIB HTTP Request node initiate and send the complete request including the payload from the initial request.

Expected:


1. IIB HTTP request node send request without payload

2. Receive the status code HTTP/1.1 100 response from web servers

3. Send the payload

4. Receive the final status code 500 or 200.


Idea priority Medium
  • Admin
    Ben Thompson
    Reply
    |
    Jan 14, 2022

    Idea / RFE Review. Thank you for taking the time to raise this enhancement request. Whilst we're not aware of anyone raising a similar request previously, and noting that you could achieve a somewhat similar usecase perhaps by using two separate HTTP invocations (one with header and no body, and a second with header and full body), we agree that there would be value in this enhancement. Status of the idea is updated to Future Consideration.