Certain `content_type` properties cause a message to disappear

[GoFightNguyen]

RabbitMQ v3.8.9 foo-foo-mq v7.0.0

foo-foo-mq appears to be dropping messages depending on the value of the content_type property. Example values in which the message is dropped:

• application/json;
• application/json; charset=UTF-8

Example values in which the message is handled:

• application/json
• no value is provided

We have a pkg that wraps foo-foo-mq in order to provide some consumer processing logic. When foo-foo-mq drops the message, neither the message nor an error are surfaced to our pkg. In addition, the message is ack'd 😦

[elizabeth-a-hobbs]

Specifically in RabbitMQ, the message is being ack'd as deliver(manual ack) when we were expecting it would be nack'd. Also, this error is only showing up by default when DEBUG=*.

We did discover that we can add a custom serializer for application/json; charset=UTF-8 and following this documentation would allow this error to be logged; however, we were expecting an error like this to be surfaced without configuration.

[zlintz]

Thanks @GoFightNguyen and @elizabeth-a-hobbs do you have a proposed change to support this functionality that you could add as a PR?

[zlintz]

Do you have a proposed solution to this problem?