Howdy! I've been upgrading an app from spring boot 2->3, and I'm seeing something odd in wiremock that wasn't true before. New version is 3.10.0 When I create a stub, the URL has ?send=true in it, but when I run the test spring webClient is sending %3fsend=true. Therefore, none of those tests pass the urlEqualTo test.

Can you share a test case that illustrates this so we can reproduce? One suggestion I’d make generally is to use query parameter matchers + URL path matching rather than matching the whole URL. This gives you more control and order invariance.

I think the webclient is encoding the URL so that ? turns into &3F. I created this test

@Test
    public void wireMockTest2() throws InterruptedException {

        wireMockServer.stubFor(<http://WireMock.post|WireMock.post>(urlPathEqualTo("/111?one=two")));
        wireMockServer.stubFor(<http://WireMock.post|WireMock.post>(urlPathEqualTo("/222?one=two")));
        wireMockServer.stubFor(<http://WireMock.post|WireMock.post>(urlPathEqualTo("/333?one=two")));

        String twostring = "two";
        Mono<String> resp = <http://scheduleMessageWebClient.post|scheduleMessageWebClient.post>().uri(uriBuilder -> uriBuilder
                        .path("/111?one={two}")
                        .build(twostring))
                .retrieve()
                .bodyToMono(String.class);
        wireMockServer.verify(1, postRequestedFor(urlEqualTo("/111?one=two")));
        Thread.sleep(5000);

    }

But every time I get back

com.github.tomakehurst.wiremock.client.VerificationException: Expected at least one request matching: {
  "url" : "/111?one=two",
  "method" : "POST"
}
Requests received: [ ]

Yes, the

Requests received: [ ]

implies that no requests arrived in WireMock. How is

scheduleMessageWebClient

being initialised and injected?

@Tom Creating web client with HttpClient httpClient = HttpClient.create() .responseTimeout(Duration.ofMillis(scheduleMessageProperties.getResponseTimeout())); return webClient(scheduleMessageProperties.getBaseURL(), oauthConfiguration.getAccessTokenUri(), oauthConfiguration.getClientId(), oauthConfiguration.getClientSecret(), "scheduleMessageClient", objectMapper, httpClient); Stub: wireMockServer.stubFor(WireMock.post(urlPathEqualTo("/111%3Fone=two"))); Call to wiremock Mono<String> resp = scheduleMessageWebClient.post().uri(uriBuilder -> uriBuilder .path("/111?one={two}") .build(twostring)) .retrieve() .bodyToMono(String.class); This returns a 404 Verify wireMockServer.verify(1, postRequestedFor(urlEqualTo("/111%3Fone=two"))); Error com.github.tomakehurst.wiremock.client.VerificationException: Expected at least one request matching: { "url" : "/111%3Fone=two", "method" : "POST" } Requests received: [ ] Where can I see what requests have been made? Also, where can I see what stubs are recorded? I’ve gone back and forth over the ? vs %3F for the stub and verify, but I can’t get a match.

Are you actually intending to put what looks like a query parameter in a path segment? Or should you be calling something like

.query("one", "two")

in your HTTP request builder code?

If I change it to wireMockServer.stubFor(WireMock.post(urlPathEqualTo("/111")).withQueryParam("one", equalTo("two")));

I mean your HTTP client, rather than WireMock

I still get a 404 'cause it's encoding the url with %3F.

Yes, but I think it’s encoding it that way because you’re saying it’s part of the path

wireMockServer.stubFor(<http://WireMock.post|WireMock.post>(urlPathEqualTo("/111")).withQueryParam("one", equalTo("two")));

scheduleMessageWebClient.post().uri(uriBuilder -> uriBuilder .path("/111").queryParam("one", "two") .build()) Returns a 404

wireMockServer.findAllUnmatchedRequests()

returns { "url" : "/operationsexecutionscheduleMessage/111?one=two", "absoluteUrl" : "http://localhost:12166/operationsexecutionscheduleMessage/111?one=two", "method" : "POST", "clientIp" : "127.0.0.1", "headers" : { "User-Agent" : "ReactorNetty/1.1.13", "Host" : "localhost:12166", "Accept" : "*/*", "Transfer-Encoding" : "chunked", "Authorization" : "Bearer ey<snip>" }, "cookies" : { }, "browserProxyRequest" : false, "loggedDate" : 1733762263678, "bodyAsBase64" : "", "body" : "", "protocol" : "HTTP/1.1", "scheme" : "http", "host" : "localhost", "port" : 12166, "loggedDateString" : "2024-12-09T163743Z", "queryParams" : { "one" : { "key" : "one", "values" : [ "two" ] } } }

Looks like you’re missing

/operationsexecutionscheduleMessage

from your stubbed URL path

It's set as the baseURL when the webclient gets created.

But it looks like you’re not including it in your stubbed URL, which is why it’s not matching and returning a 404

Wow. I spent two days looking for that. 😅 If I do it that way I still see com.github.tomakehurst.wiremock.client.VerificationException: Expected at least one request matching: { "urlPath" : "/operationsexecutionscheduleMessage/111", "method" : "POST", "queryParameters" : { "one" : { "equalTo" : "two" } } } Requests received: [ ]

Are you definitely setting the base URL to WireMock for the WebClient? I didn’t see that in your code snippet.

It's in the webClient contrstrutor.

No worries, no pint required 🙂