Using the x-mock-match-request-headers will not return default response when header is not passed

[jwbanning]

Describe the bug
While using a the x-mock-match-request-headers against my mock server, the default response is not returned when nothing is passed in the header.

To Reproduce
Steps to reproduce the behavior:

1. Set up a mock server with 3 examples.
   a. Default example. Response should be

{
	number:default
}

b. Example ONE.  key: values of number:one is set for the header. Response should be 

{
	number:one
}

c. example named TWO when a key: values of number:two is set for the header. Response should be

{
	number:two
}

2. Send the request with the different header parameters:
   number: one | two
   x-mock-match-request-headers: number

This works correctly.

3. Send the request without any header parameters

and the response is the example when the header value is one:

{
	number:one
}

Expected behavior
When nothing is passed in the header, the default response would return.

I have made a couple videos that I can share to illustrate the issue.

[pranayat]

Hi,
When nothing is passed in the header then all 3 examples become equal candidates for a response and one of them is chosen.
This happens because when the x-mock-match-request-headers header is not sent (or no value is set therein), the headers set in the example requests are ignored.
Hence, the examples 'default', 'ONE' and 'TWO' are all treated equally (I'm assuming they all have the same path). In your case, example 'ONE' was chosen.
Do let me know if this cleared things up. If not, do share the videos you made.

[jwbanning]

meow.mov <https://drive.google.com/file/d/1GgppFq_rFef_xy6nh0X_oUibDIM1JvTq/view?usp=drive_web> I am still unsure. I would think when i do not pass anything in the header the default example would hit.. See the movie

…

On Mon, Feb 17, 2020 at 10:47 PM Pranaya Tomar ***@***.***> wrote: Hi, When nothing is passed in the header then all 3 examples become equal candidates for a response and one of them is chosen. This happens because when the x-mock-match-request-headers header is not sent (or no value is set therein), the headers set in the example requests are ignored. Hence, the examples 'default', 'ONE' and 'TWO' are all treated equally. In your case, example 'ONE' was chosen. Do let me know if this cleared things up. If not, do share the videos you made. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#8065?email_source=notifications&email_token=AATW5QSDHMSC2AVJG5KRMX3RDNR53A5CNFSM4KVMSDY2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMASBOI#issuecomment-587276473>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AATW5QRDVEKIRHT3KUVLWMDRDNR53ANCNFSM4KVMSDYQ> .

[pranayat]

All 3 examples are identical if their headers are ignored. The headers are ignored if the x-mock-match-request-headers header is not sent (or is empty). Hence any one of the 3 may be chosen (though the same one will be chosen every time). There is no construct of 'priority' or 'ordering' or 'default' among identical examples in Postman currently.