Investigate AMQP deserialisation for repeated field-values

Description

Investigate the AMQP deserialisation logic to see what happens when field-values are repeated.

Quoting on #development channel:

"we receive a message on the wire that maps to class Foo(val a: String, val b: String). but the on-wire representation is something like a: "Foo" b: "Bar" a: "Baz" - what happens?"

Todo:

  • Understand what the existing behaviour is - is this classed as message corruption or does the duplicate field value parsed & accepted?

  • Does this match up with what the expected behaviour is?

  • Add any necessary test cases to cover this scenario

Assignee

James Brown

Reporter

James Brown

Feature Team

Security Research

Story Points / Dev Days

5

Fix versions

None

Ported to...

None

Engineering Teams

None

Priority

High
Configure