Tom Akehurst

We need to be a bit careful here. IIRC we use the Guava encoder because it's quite a lot faster than than the one from `java.util`. I'm pretty sure we'd...

Nope, added in 7818ed00ebf5cbebbd505480c57a2db78f9afb60

Here's my suggested design for this: ```java stubFor(get(urlPathEqualTo("/things")) .withQueryParam("id", havingExactly("1", "2", "3")) // There must be 3 values of id exactly whose values are 1, 2, and 3 .willReturn(ok())); stubFor(get(urlPathEqualTo("/things"))...

I've been thinking about this on and off, and I agree it would be very useful in some circumstances. However, I think there are a number of tricky design choices...

Please can you share all the steps necessary to reproduce this? A working test case would be ideal.

Think we still need a test case for this. Although this code is exercised generally by the acceptance tests, there's nothing that produces the problem this is attempting to fix.

Now obsolete as we've moved back to the JDK encoder

Has anyone had a chance to test this with 3.0.0-beta-4?

Pretty sure that's still 2.x

@du-it can I suggest you head over to the WireMock Slack and post the details of what you're seeing?