Server Receives Message with Header Value gives false positive

I was running the acceptance test and came across this when I ran the following Test case after modifiying the value for **header:reserved:0xff** to **header:reserved:0xaa**
- Atest
- Default Values
- Default values for header fields

Here's the Test Case with the modified Keyword

```
"""
Client sends Header value ExampleMessage
${msg}= Server receives Header value 0xAA ExampleMessage
Should be equal ${msg._header.reserved.hex} 0xff
"""
```

Here's the Modified Keyword
Header value 0xAA ExampleMessage

```
"""
Value ExampleMessage**
Value header:reserved 0xaa
"""
```

With the Keyword Modified above, the test case should have failed.
It seems like specifying the header value for reserved is making no effect.

My Apologies if I am not understanding this correctly.

Please correct me if I am wrong.

Thanks,
Harsh

Start by reproducing the acceptance test under “Atest / Default Values / Default values for header fields” using the shown “Header value” keyword and reserved-header values. Inspect how the keyword applies header:reserved and verify whether changing it to 0xaa affects the received message. Done means the modified case no longer produces a false positive and the expected assertion behavior is covered.

Written by the indexing model from the issue text.