Exception in parseBody (parseWSManResponseBody.ts)

[orinem]

Describe the bug 🪲

It's possible for AMT to return status code 400 with no body (Content-Length: 0). In this case, parseBody() attempts to access message.body.text and throws an exception.

To Reproduce 🪜

It may well occur randomly due to an underlying problem with splitting writes of a request using chunked encoding to CIRA channels. This pull request discusses one such case

Expected behavior

A suitable error should be returned, either '' or null. It could be as simple as:

  if (message.bodySize === 0) {
    return ''
  }

Alternatively, it shouldn't even be called if bodySize is zero.

AMT Device (please complete the following information): 🖥️

• OS: Windows
• AMT Version: 15.0.41
• AMT Configuration Mode: CCM
• Network Configuration: Dynamic IP

Service Deployment (please complete the following information): ⛈️

• Deployment Type: Docker
• Node Version: 16
• Component & Version: mps latest

Additional context

Debug trace showing message object passed to parseBody():

2022-08-01T18:54:20.997Z silly: parseBody: {
        "protocolVersion": "HTTP/1.1",
        "statusCode": 400,
        "statusMessage": "Bad Request",
        "headersSize": 143,
        "bodySize": 0,
        "headers": [
                {
                        "name": "Date",
                        "value": "Mon, 1 Aug 2022 18:54:20 GMT"
                },
                {
                        "name": "Server",
                        "value": "Intel(R) Active Management Technology 15.0.41.2142"
                },
                {
                        "name": "Content-Length",
                        "value": "0"
                }
        ]
}
2022-08-01T18:54:20.997Z error: Exception during alarm occurrences request : TypeError: Cannot read properties of undefined (reading 'text')
2022-08-01T18:54:20.998Z info: TypeError: Cannot read properties of undefined (reading 'text')
    at parseBody (/mps-microservice/dist/utils/parseWSManResponseBody.js:13:25)