APAR status
Closed as program error.
Error description
HTTPRequestHeader when reconstructed from bitstream, using PARSE ESQL statement, is seen throwing "BIP6105E : The remaining bitstream is too small to contain an ''HTTPRequestHeader'' structure." and "BIP3159E : An error was found whilst parsing HTTP header data. The data is not an HTTP Request or Response. Invalid HTTP Header data." errors. The issue occurs when the serialized header bitstream is missing either of X-Original-HTTP-Command or X-Original-HTTP-Status-Line header element.
Local fix
Make sure that the HTTPRequestHeader folder contains either X-Original-HTTP-Status-Line or X-Original-HTTP-Command header before serializing it to the bitstream. If not present, add them explicitly. For eg: Set OutputRoot.HTTPRequestHeader.X-Original-HTTP-Status-Line='H TTP/1.1200 OK' or Set OutputRoot.HTTPRequestHeader.X-Original-HTTP-Command='POST http://dummyhost'
Problem summary
**************************************************************** USERS AFFECTED: All users of IBM App Connect Enterprise V11.0 and V12 who uses HTTP Request node Platforms affected: MultiPlatform **************************************************************** PROBLEM DESCRIPTION: HTTPRequest header parser may fail if you try to reconstruct the headers from the bitstream. For example: If you use the following ESQL, DECLARE myBlob BLOB X'417574686F72697A6174696F6E3A204261736963206173646A6B6E616C6B6A 73646E6C616A736B646C616B73646C0D0A582D4F726967696E616C2D48545450 2D5374617475732D4C696E653A485454502F312E3120323030204F4B'; CREATE LASTCHILD OF OutputRoot DOMAIN('HTTPRequestHeader') PARSE(myBlob); it may throw below errors: "BIP6105E : The remaining bitstream is too small to contain an ''HTTPRequestHeader'' structure." and "BIP3159E : An error was found whilst parsing HTTP header data. The data is not an HTTP Request or Response. Invalid HTTP Header data." The reason being that the HTTP headers parser will always look for a request-line like(POST http://xyz) or response line (200 0K) at the starting of bitstream; but if the bitstream contains only header fields in 'name:value' form, the parser fails.
Problem conclusion
The product has been modified so that the HTTPRequest parser will now accept bitstreams that don't contain a request/response line upfront. Additionally, bitstreams in the form of name:value pairs will be able to be reconstructed back into HTTP headers. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v11.0 11.0.0.23 v12.0 12.0.10.0 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
IT38722
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-10-18
Closed date
2023-08-23
Last modified date
2023-08-23
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
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDR5J","label":"IBM App Connect Enterprise"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B00","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
24 August 2023