Invalid Destination Set Filtering test case defaults to last destination

[phommata]

Is it expected that HTTP Listener requests will default to the last destination when they meet none of the destination set filters conditions?

I am building an HTTP Listener with a few destinations to support different URIs, i.e. /base/path1 and /base/path2. The destination set filtering work as expected to remove except the corresponding destinations, i.e. destination 1 and destination 2.

These behave as expected:

GET /base/path1 -> destination 1 (remove all except)
GET /base/path2 -> destination 2 (remove all except)

When I make a GET request to a non-existent URI segment, i.e. /base/path3, the request defaults to the last destination, i.e. destination 2. I had expected the request to not be processed for not meeting the destination set filtering condition. Is this behavior correct?

Unexpected behavior when using an invalid test case:

GET /base/path3 -> destination 2 (remove all except last destination)

To work around that default behavior sending to the last destination, I created an additional destination to handle other cases. i.e.:

GET /base/path3 -> destination 3 (remove all except last destination)
GET /base/path4 -> destination 3 (remove all except last destination)
...