You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Replay files seem to search for the first header when testing and assume that is the intended value. This is fine except for duplicate headers.
E.g.
X-Duplicate-Header: same
X-Duplicate-Header: other
It would then fail like this [INFO]: Equals Violation: Different. Key: "fill_1", Field Name: "x-duplicate-header", Correct Value: "other", Actual Value: "same" : 26
Despite that other is the intended value for the second duplicate header
The text was updated successfully, but these errors were encountered:
Replay files seem to search for the first header when testing and assume that is the intended value. This is fine except for duplicate headers.
E.g.
X-Duplicate-Header: same
X-Duplicate-Header: other
It would then fail like this
[INFO]: Equals Violation: Different. Key: "fill_1", Field Name: "x-duplicate-header", Correct Value: "other", Actual Value: "same" : 26
Despite that other is the intended value for the second duplicate header
The text was updated successfully, but these errors were encountered: