IIRC it will usually try to determine which mode to use based on the request entity object. If it can determine the length it’ll send the Content-Length header, otherwise it’ll go chunked.

i'll try and look in the code and see if it is being set

might be a bug in their sdk

hmm, seems i can only work with jre8-standalone

Because there’s a conflicting version of HTTPClient in the non-standalone version?

i think so

between gradle + our dependency

4.5.14 (sdk + org.springframework.cloudspring cloud test support4.0.0) 5:5.1.4 (org.springframework.cloudspring cloud contract wiremock4.0.0) + gradle also seemed to have it bundled in (gradle 7.6 - 4.4.16 + kotlin gradle plugin 1.8)

I think 4 and 5 should be able to cohabit, since 5 has got

client5

in its artifact name and packages

Having said that at the moment standalone is usually the best bet when working with Spring. Is there a specific issue you have with that one?

just fails to bind now i think

Can you share the details? I know many teams use standalone as a dependency with Spring, including the Spring Cloud Contract team, so it should work OK.

prob my code, will check

on latest 3. beta version?

The 3.x beta fixes the main reason you need to use standalone, so with that you should be able to use either. If you want to use 2.x with Spring Boot 3.x you’ll need standalone.

would like to say thanks for all the help you have given so far!

No problem!

Hello! I have been trying to port our tests from MockServer to WireMock at work. Sadly it hasn't gone as smooth as I was hoping. I hit some issues, was hoping you could give a few ideas. I had some original questions but in the time being WireMockServer completely stopped working 😅

Not listening on HTTP port. Either HTTP is not enabled or the WireMock server is stopped.
java.lang.IllegalStateException: Not listening on HTTP port. Either HTTP is not enabled or the WireMock server is stopped.
	at wiremock.com.google.common.base.Preconditions.checkState(Preconditions.java:444)
	at com.github.tomakehurst.wiremock.WireMockServer.port(WireMockServer.java:179)

Found this: https://github.com/bakdata/fluent-kafka-streams-tests/issues/22 and this: https://groups.google.com/g/wiremock-user/c/4kkOMn58CzM?pli=1 JUnit version

4.13.2

testImplementation "junit:junit:4.13.2"

Being going through the recently merged code to see what could have caused this in the past 24 hours but I can't quite tell.

private Environment newEnvironmentInstance(.....) {
        .... some code here .... 

        final WireMockConfiguration config = wireMockConfig().dynamicPort();
        final WireMockServer mockServer = new WireMockServer(config);
        environment.setUrl(URI.create("<http://localhost>:" + mockServer.port()));
        environment.setService(URI.create("<http://localhost>:" + mockServer.port()));
        environment.setInitial(initial);
        <http://logger.info|logger.info>("Environment started: {} on port {} ({})",
                environment.getId(), mockServer.port(), environment.getName());

        mockServer.start();

        mockServer.stubFor(.....)
  }

Any thoughts what might have caused this?

Hi @Sinan Pehlivanoglu you need to call

mockServer.start()

before

mockServer.port()

since when you use dynamically assigned ports they’re only assigned at startup.

Thank you!

This message was deleted.

Hello, I'm using wiremock to test mutual ssl connection with an external API. But i'm getting this error

client_cacerts.jks is not a valid keystore

, although it is valid , here is the code

WireMockServer wireMock = new WireMockServer(wireMockConfig()
      //.port(8080)
      .httpsPort(8443)
      .needClientAuth(true)
      .keystoreType("jks")
      .keystorePath("client_keystore.jks") // Either a path to a file or a resource on the classpath
      .keystorePassword("secret")
      .keyManagerPassword("secret")
      .trustStorePath("client_cacerts.jks")// The password used to access the keystore. Defaults to "password" if omitted
      .trustStorePassword("secret")
);
@Test
void test() {
   wireMock.start();
   wireMock.stubFor(
         WireMock.get("/hello")
               .willReturn(WireMock.ok("world"))
   );

Any thoughts what might be causing this error ?

This message was deleted.

Hi everyone, hope my message finds you well. I am using wiremock docker image and I am working on some security vulnerabilities founded, for example in the sqlite version (SQLite 1.0.12 through 3.39.x before 3.39.2 sometimes allows an array-bounds overflow if billions of bytes are used in a string argument to a C API.) is something that I should ignore or someone can help me to upgrade the version? In advance, thanks for your help!

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

Hello I've a question for someone expert in wiremock

We're using wiremock-studio:2.32.0-18 docker image, I'm trying to pass some arguments to the docker image in order to customize it, for example enabling HTTPS but the wiremock throw an error

wiremock    | Exception in thread "main" joptsimple.UnrecognizedOptionException: https-port is not a recognized option