IBM Support

IT22470: REST API URL MATCHING SOMETIMES RESOLVING TO WRONG OPERATION WHEN MULTIPLE SIMILAR MATCHING URLS REGISTERED

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 a REST API has the following definition where there are
    overlaps at the same level, for example if there following two
    operations were defined:
    
        Method: GET
           Url: l1/{variable}/{variable2}
     Operation: op1
    
        Method: GET
           Url: /l1/l2/{variable3}
     Operation: op2
    
    and a request is made to url /l1/l2/12345 then it is possible
    that the url will invoke operation op1 instead of op2 which is
    what should be invoked as literals take preference over
    variables.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    All users of IBM Integration Bus V10 and the RESTInput node.
    
    
    Platforms affected:
    MultiPlatform, z/OS
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    If a REST API has the following definition where there are
    overlaps at the same level, for example if there following two
    operations were defined:
    
        Method: GET
           Url: l1/{variable}/{variable2}
     Operation: op1
    
        Method: GET
           Url: /l1/l2/{variable3}
     Operation: op2
    
    and a request is made to url /l1/l2/12345 then it is possible
    that the url will invoke operation op1 instead of op2 which is
    what should be invoked as literals take preference over
    variables.
    
    When registering the URLs they are not always ordered
    correctly for runtime resolution and the registration was not
    sorting them correctly.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT22470

  • Reported component name

    INTEGRATION BUS

  • Reported component ID

    5724J0540

  • Reported release

    A00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-09-20

  • Closed date

    2017-11-28

  • Last modified date

    2017-11-28

  • 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

    INTEGRATION BUS

  • Fixed component ID

    5724J0540

Applicable component levels

  • RA00 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 November 2017