content.text should never be `null`

[kennethklee]

Agent always sends request.content.text and response.content.text. They should be omitted if text doesn't exist.

[ahmadnassri]

no, this is wrong. current behaviour is correct.

[SGrondin]

As discussed with Ahmad previously, this is how it works:

• If replays on the agent/proxy are enabled, then there must be a Content object.
• If replays are enabled, there must be a text property.
• In case of an empty body, the text field will contain an empty string.

There is never any null. ever. ever. ever.

ever.

[kennethklee]

Just discussed with Ahmad. Null means the agent failed to process the body.

[SGrondin]

I don't understand how it could fail to base64-encode a string in the first place, but ok. It just seems like a hack to me.