APAR status
Closed as program error.
Error description
If the Integration Node 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 http input 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. *Note : Apar IT22762 addresses the same issue when the application is using embedded http listener.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: All users of IBM Integration Bus V10.0 using the HTTP Input node with wildcards in the URL and using the Integration Node HTTP Listener. Platforms affected: z/OS, MultiPlatform **************************************************************** PROBLEM DESCRIPTION: If the Integration Node HTTP Listener is listening on address http://localhost:7080, and receives the request http://localhost:7080/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 HTTP input 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 correct HTTPInput node message flow. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v10.0 10.0.0.21 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
IT26633
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
2018-10-26
Closed date
2020-06-12
Last modified date
2020-07-01
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
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQK6","label":"IBM Integration Bus"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
02 July 2020