LI81547: COMPATABILITY MODULE APIM.JS SETVARIABLE FUNCTION MUST SET THE MESSAGE CONTENT-TYPE HEADER TO UNKNOWN

APAR status

• Closed as program error.

Error description

• To be compatible with API Connect v5, the apim.setvariable
  function must set the message content type to "unknown".
  Version 5 did not make the assumption that the content type
  already in place did not change when the message body was
  updated. Setting the content type to unknown forced the user to
  also use an apim.output function to specify the content type of
  the data just written, but if they omitted doing this, the
  unknown value would prevent a mismatch of the payload content
  and a content type for a XML or JSON payloads should the actual
  payload be different from the original content type.
  

Local fix

Problem summary

• The apim functions are v5 compatibility functions.  The
  setvariable function was not compatible with v5 in that it did
  not change the content type header to "unknown" when
  message.body was used.  If the code did not also do a
  apim.output function to specify the content type of the
  message.body just set, this would allow the potential for a
  subsequent policy to parse message.body based upon the current
  content type even though the content-type didn't match the
  body's type, causing an error.
  

Problem conclusion

• <span style="background-color:rgb(255, 255, 255);color:rgb(34,
  34, 34);font-family:lato,helvetica
  neue,helvetica,arial,sans-serif">The fix is targeted for
  inclusion in IBM API Connect fixpack </span><span
  style="background-color:rgb(255, 255, 255)">version
  2018.4.1.12.</span>
  

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:

Fix information

• Fixed component name

  API CONNECT ENT

• Fixed component ID

  5725Z2201

Applicable component levels

• R18X PSY

     UP