Header Duplication with Application Version set as Application ID
Summary
(Summarize the bug encountered concisely)
Steps to reproduce
Produce any message with the lineage proxy enabled. Set the Application ID and no Producer Version Test this on a cluster with Value headers enabled
Example Project
N/A
What is the current bug behavior?
The Application Version, which defaults to unknown is set as the Application ID header Message-ID has the correct GUID and a 0 GUID All Headers are duplicated
What is the expected correct behavior?
The Application Version is set as the Application Version header The Message-ID header should just be the GUID No duplication of headers
Relevant logs and/or screenshots
Name Length Data (String) Data (Hex)
Axual-Message-Id 16 <binary>. <masked>
Axual-Producer-Id 36 my.application.id <masked>
--- Axual-Producer-Id 7 Unknown <masked>
Axual-Serialization-Time 8 <binary> <masked>
Axual-Copy-Flags 4 <binary> 0000
Axual-System 18 <masked> <masked>
Axual-Instance 3 <masked> <masked>
Axual-Tenant 4 <masked> <masked>
Axual-Environment 9 <masked> <masked>
Axual-Cluster 12 <masked> <masked>
Axual-Serialization-Time 8 <binary> <masked>
Axual-Copy-Flags 4 <binary> <masked>
--- Axual-Message-Id 16 <binary> <masked>
Axual-Deserialization-Time 8 <binary> <masked>
Axual-Environment 9 <masked> <masked>
Axual-Tenant 4 <masked> <masked>
Axual-Intermediate-Id 36 my.application.id <masked>
Axual-Intermediate-Version 7 Unknown <masked>
Axual-System 18 <masked> <masked>
Axual-Instance 3 <masked> <masked>
Axual-Cluster 12 <masked> <masked>
Possible fixes
Use the proper header
Edited by Richard Bosch