Match query string parameters as a set of name/value pairs

I’ve been using the WireMock record feature to create a mock of a REST API. The generation works pretty well, except that the matching of query strings in URLs seems to be a basic string equality type of match. This is fine for single parameter query strings, but means that URLs with multiple parameters MUST honour the order used in the recording (mappings), which isn’t much use. The query string should be considered as a set of (unordered) name/value pairs and matched as such.

The following URLs should be considered identical:

• examlpe.com/path?number=1&string=hello&date=01-01-1970
• examlpe.com/path?number=1&date=01-01-1970&string=hello
• examlpe.com/path?string=hello&date=01-01-1970&number=1
• examlpe.com/path?string=hello&number=1&date=01-01-1970
• examlpe.com/path?date=01-01-1970&string=hello&number=1
• examlpe.com/path?date=01-01-1970&number=1&string=hello

[fraserharris]

Has this been fixed? From my testing:

get(urlPathMatching("/3.0/resource/"))
                        .withQueryParam("count", WireMock.equalTo("1"))
                        .withQueryParam("offset", WireMock.equalTo("2"))
                        .withQueryParam("apikey", WireMock.equalTo(ACCESS_TOKEN)),

Creates:

{
  "urlPathPattern" : "/3.0/resource/",
  "method" : "GET",
  "queryParameters" : {
    "count" : {
      "equalTo" : "100"
    },
    "offset" : {
      "equalTo" : "1"
    },
    "apikey" : {
      "equalTo" : "mock_access_token"
    }
  }

[gr423]

Hi Tom ,

I’ve created the issue #978

Thanks ,