IBM Support

IT36348: HTTPINPUT NODE URL MATCH CAN GO WRONG IF MULTIPLE HTTPINPUT NODES ARE DEPLOYED WITH WILDCARD (ASTERISK) IN THE URL.

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • If the HTTP listener is listening on address
    http://localhost:7080, and receives the request
    http://localhost:7800/Joe/Mary, the listener removes the HTTP
    address, leaving the request Joe/Mary. The listener then matches
    this request with the information that is specified in the URL
    property of the HTTPInput node or nodes. The match is done from
    the most specific to the most generic data; you can use a
    wildcard (an asterisk) to satisfy less specific matches. But if
    multiple HTTPInput nodes are deployed with a wildcard in the
    URL, then the most specific URL is not always picked up if there
    is not an exact match available.
    
    For example, if two HTTPInput nodes are deployed with URLs
    '/match/v1/*' and '/match/v1/api/*' and an HTTP request is
    received with URL '/match/v1/api/test', then it may get matched
    against URL '/match/v1/*' instead of the more specific one of
    '/match/v1/api/*'. Also if a message flow is deployed with URL
    as '/*', then all the requests can get routed to this flow.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM App Connect Enterprise V11.0 using the HTTP
    Input node with wildcards in the URL.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    If the HTTP listener is listening on address
    http://localhost:7080, and receives the request
    http://localhost:7800/Joe/Mary, the listener removes the HTTP
    address, leaving the request Joe/Mary. The listener then matches
    this request with the information that is specified in the URL
    property of the HTTPInput node or nodes. The match is done from
    the most specific to the most generic data; you can use a
    wildcard (an asterisk) to satisfy less specific matches. But if
    multiple HTTPInput nodes are deployed with a wildcard in the
    URL, then the most specific URL is not always picked up if there
    is not an exact match available.
    
    For example, if two HTTPInput nodes are deployed with URLs
    '/match/v1/*' and '/match/v1/api/*' and an HTTP request is
    received with URL '/match/v1/api/test', then it may get matched
    against URL '/match/v1/*' instead of the more specific one of
    '/match/v1/api/*'. Also if a message flow is deployed with URL
    as '/*', then all the requests can get routed to this flow.
    

Problem conclusion

  • The product now routes the incoming HTTP request to the
    HTTPInput node message flow that satisfies most specific URL if
    there is not an exact match available.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v11.0      11.0.0.13
    
    The latest available maintenance can be obtained from:
    http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
    
    If the maintenance level is not yet available,information on
    its planned availability can be found on:
    http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT36348

  • Reported component name

    APP CONNECT ENT

  • Reported component ID

    5724J0550

  • Reported release

    B00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-03-25

  • Closed date

    2021-06-02

  • Last modified date

    2021-06-02

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    APP CONNECT ENT

  • Fixed component ID

    5724J0550

Applicable component levels

[{"Line of Business":{"code":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSDR5J","label":"IBM App Connect Enterprise"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B00"}]

Document Information

Modified date:
03 June 2021