PI81379: ERROR 400 BAQR7018E: The HTTP request is missing parameter <parm_name>

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• A request sent to z/OS Connect EE receives an error 400 response
  and the following message is written:
  BAQR7018E: The HTTP request is missing parameter <parm_name>
  reporting that a specific header parameter is not present, even
  though that parameter is present in the header sent.
  
  Further investigation showed that this error was seen when the
  first and subsequent requests contained the same parameter name
  with different capitalization. For example, if the http header
  name passed on the http channel was "abcdEFG", but if the first
  header name was "abcedfg" the BAQR7018E message is written.
  
  Additional search words: msgBAQR7018E msgBAQR7018 BAQR7018
  

Local fix

• Restart the z/OS Connect V2 EE server with the --clean
  parameter to clear the http header cache.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of z/OS Connect EE V2              *
  ****************************************************************
  * PROBLEM DESCRIPTION: Error 400 returned and msgBAQR7018E:    *
  *                      The HTTP request is missing parameter   *
  *                      <parm_name>                             *
  ****************************************************************
  The problem is caused by the header name of the first flow
  being cached and subsequent requests being compared to the
  first in a case sensitive manner. If the capitalization of the
  header parameter name in the first flow differs from
  that of subsequent flows, no match is found and the reported
  message is issued.
  
  This mismatch is not clarified by a conflict between two
  specifications relevant in this scenario.
  
  The HTTP/1.1 Specification RFC2616 section 4.2 Message Headers
  indicates the headers are case insensitive:
  https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2
  
  The Swagger 2.0 Specification for Format indicates all field
  names are case sensitive:
  http://swagger.io/specification/
  

Problem conclusion

• z/OS Connect EE has been changed so that the comparison of
  http header parameters names is not case senstive.
  

Temporary fix

Comments

APAR Information

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

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

  PI84080

Modules/Macros

• BAQ00002 BAQ00081 BAQ00107 BAQ00126 BAQ00130 BAQ00142 BAQ00146
  BAQ00147 BAQ00148 BAQ00149 BAQ00150 BAQ00151 BAQ00152 BAQ00153
  BAQ00154 BAQ00155 BAQ00156 BAQ00157 BAQ00158 BAQ00159 BAQ00160
  BAQ00161 BAQ00162 BAQ00163 BAQ00164 BAQ00165 BAQ00166 BAQ00167
  BAQ00168 BAQ00169 BAQ00170 BAQ00171 BAQDIRSH BAQMKDIR BAQWLPAX
  

Fix information

• Fixed component name

  Z/OS CONNECT EN

• Fixed component ID

  5655CEE00

Applicable component levels

• R200 PSY UI48949

     UP17/07/22 P F707

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.