bug: multiple header value matching semantics #213
Description
HTTP headers can have multiple values for the same key.
Clarify what should be the route matching behavior for headers with multiple values to avoid surprises for the end user when they switch from one implementation to other.
A good example for this is matching based on X-forwarded-for header.
Questions to be answered:
- Should a single match for value among a set of values be considered a positive match?
- Should it be required to list out all values in case of multiple headers for a valid match? Is ordering important in this case?