mirror of
http://git.haproxy.org/git/haproxy.git/
synced 2024-12-27 07:02:11 +00:00
3b0bf5097b
Willy made me realize that tree-based matching may also suffer from
out-of-order mapfile loading, as opposed to what's being said in
b546bb6d ("BUG/MINOR: map: list-based matching potential ordering
regression") and the associated REGTEST.
Indeed, in case of duplicated keys, we want to be sure that only the key
that was first seen in the file will be returned (as long as it is not
removed). The above fix is still valid, and the list-based match regtest
will also prevent regressions for tree-based match since mapfile loading
logic is currently match-type agnostic.
But let's clarify that by making both the code comment and the regtest
more precise.
7 lines
225 B
Plaintext
7 lines
225 B
Plaintext
# These entries are used for list-based match ordering tests
|
|
first.domain.tld first
|
|
domain.tld domain
|
|
second.domain.tld second
|
|
# This entry is used to test duplicate behavior (ie: tree-based match)
|
|
first.domain.tld first_dup
|