Message's body is miscategorized as XML when the Content-Type header is missing

[afprtclr]

Symptoms

Non-XML messages are stored with text/xml as the content type value, which might result in errors in ServicePulse when visualizing or editing the message body.

Who's affected

Users sending messages with no Content-Type header. This is supposedly affecting native integration only.

Root cause

In case of missing Content-Type, text/xml is assumed as default.

Confirmed workarounds

N/A

Original bug report

Describe the bug

Description

When a message with no Content-Type header is delivered to ServiceControl, it is treated as if it was a text/xml message. This further breaks ServicePulse since it cannot pretty-print such a message.

Expected behavior

Message is stored as text/plain

Actual behavior

Message is stored as text/xml

[swarupio]

@afprtclr Hi i want to contribute to this issue , also can you please add hacktoberfest tag to it!

[afprtclr]

@swarupio Thanks for reaching out. Unfortunately, the fix has already been merged in #5140 and the only remaining thing is the release. Nevertheless, we'd love your contributions in other issues and we appreciate that you're willing to take time to improve the code base.

[swarupio]

@swarupio Thanks for reaching out. Unfortunately, the fix has already been merged in #5140 and the only remaining thing is the release. Nevertheless, we'd love your contributions in other issues and we appreciate that you're willing to take time to improve the code base.

Sure! I would love to contribute.

[abparticular]

Will be shipped in 6.7.4