IBM webMethods Hybrid Integration

IBM webMethods Hybrid Integration

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.


#TechXchangePresenter
 View Only
Expand all | Collapse all

APIGW is not accepting square brackets in request data

  • 1.  APIGW is not accepting square brackets in request data

    Posted Wed June 07, 2023 07:51 AM

    Product/components used and version/fix level:

    API Gateway

    Detailed explanation of the problem:

    The API-GW doesn’t accept square brackets in the data of the request.

    Error messages / full error message screenshot / log file:

    The following curl request fails:

    curl -X POST ‘http://apigw-host:5555/httptest/updatedata’ --header “Content-Type: application/json” --header “User-Agent: localAgent” --header “X-Forwarded-For: 192.168.2.20” -d ‘[{“param1”:“value1”},{“param1”:“value2”}]’

    The error from the Gateway is:

    {“Exception”:"API Gateway encountered an error. Error Message: Native service provider error. Code : 400. … }

    If I remove the square brackets, the request goes through.

    Question related to a free trial, or to a production (customer) instance?

    Yes, I downloaded the 10.15 free trial docker image for our evaluation.


    #API-Gateway
    #API-Management
    #webMethods


  • 2.  RE: APIGW is not accepting square brackets in request data

    Posted Wed June 07, 2023 11:37 AM

    What leads to the conclusion the API GW does not accept the array in the HTTP body?

    The error message indicates that the service that GW forwards the payload to (the native service provider) threw the error. Do you have more information about what the native service provider received and what it did?


    #API-Gateway
    #webMethods
    #API-Management


  • 3.  RE: APIGW is not accepting square brackets in request data

    Posted Fri June 09, 2023 02:52 AM

    I checked the pcaps. I am not sure why this issue occurs. When I directly access the backend server, with the same API, it goes through. But when I accessed the API through the API GW, the server was returning 400.

    The problem was with my backend server, when accessed via the API GW.

    This is not an issue with the API GW.


    #API-Management
    #webMethods
    #API-Gateway