You need to tell it explicitly to proxy through WireMock, then what you’ve got should work

What i'm trying to figure out is, can I get wiremock to fail the request since it's not stubbed explicitly

(oh! and thank you so much for your help / quick responses btw!)

oh, let me take back that it's definitely proxying, i could be misreading the logs

but, if I change the request to use

<http://www.example.com/test|www.example.com/test>

, wiremock does return the stubbed response

so that makes me think that wiremock is intercepting this

Try this:

val wm = WireMockExtension.newInstance()
          .options(wireMockConfig()
                  .enableBrowserProxying(true)
                  .proxyPassThrough(false)
          )
          .failOnUnmatchedRequests(true)
          .build()

that sounds promising

one sec

I think that disabled the proxying all together in my use case. I'm getting the same http response (when I'd expect to get an assertion error because no stub matched), and I'm also not getting the logs I used to get that seemed to show that wiremock accepted the request and was proxying it through

kk, so I don't think it's quite doing what i'm expecting. I changed the example a bit to use http://httpbin.org/get Scenario 1: proxyMode = false (works as expected)

val wm = WireMockExtension.newInstance()
//            .options(WireMockConfiguration.wireMockConfig()
//                .enableBrowserProxying(true)
//                .proxyPassThrough(true)
//            )
            .proxyMode(false)
            .failOnUnmatchedRequests(true)
            .build()

If i use this config (which should disable all proxying and any request I send shouldn't interact with wiremock at all) and then stub/call like this:

wm.get {
  url contains "get"
}.returns { statusCode = 201 }

val client = HttpClientBuilder.create().useSystemProperties().build()
val resp = client.execute(HttpGet("<http://httpbin.org/get>"))
println(resp.statusLine)
println(resp.entity.content.readAllBytes().toString(Charsets.UTF_8))

I'll see the actual response which is good:

HTTP/1.1 200 OK
{
  "args": {}, 
  "headers": {
    "Accept-Encoding": "gzip,deflate", 
    "Host": "<http://httpbin.org|httpbin.org>", 
    "User-Agent": "Apache-HttpClient/4.5.14 (Java/21.0.3)", 
    "X-Amzn-Trace-Id": "Root=1-66799f0a-0d6d0e1e08c6c00f24cdb810"
  }, 
  "origin": "184.165.15.27", 
  "url": "<http://httpbin.org/get>"
}

Scenario 2: proxyMode = true (stubbing works, but non stubs flow through)

val wm = WireMockExtension.newInstance()
//            .options(WireMockConfiguration.wireMockConfig()
//                .enableBrowserProxying(true)
//                .proxyPassThrough(true)
//            )
            .proxyMode(true)
            .failOnUnmatchedRequests(true)
            .build()

// ...

wm.get {
  url contains "get"
}.returns { statusCode = 201 }

val client = HttpClientBuilder.create().useSystemProperties().build()
val resp = client.execute(HttpGet("<http://httpbin.org/get>"))
println(resp.statusLine)
println(resp.entity.content.readAllBytes().toString(Charsets.UTF_8))

I'll see the 201 response in this case which is expected. But if I changed to a different path, i'd just get the response from origin back instead of a failure. Scenario 3: proxyPassThrough = false (does not work as expected)

val wm = WireMockExtension.newInstance()
            .options(WireMockConfiguration.wireMockConfig()
                .enableBrowserProxying(true)
                .proxyPassThrough(false)
            )
//            .proxyMode(false)
            .failOnUnmatchedRequests(true)
            .build()

wm.get {
            url contains "get"
        }.returns { statusCode = 201 }

        val client = HttpClientBuilder.create().useSystemProperties().build()
        val resp = client.execute(HttpGet("<http://httpbin.org/get>"))
        println(resp.statusLine)
        println(resp.entity.content.readAllBytes().toString(Charsets.UTF_8))

With this config, I get the same response as scenario 1 unfortunately, it seems like no proxying is happening at all and wiremock isn't involved in the request. If I changed

proxyPassThrough(true)

nothing changes as well.

I'm following the instructions from the docs here which mention that useSystemProperties sets up the auto proxy config

regardless, since i'm new the java ecosystem, maybe you could point me in the right direction for my problem. Given a library that you don't have good control over how the internal http requests are created, how would you go about stubbing out that functionality? Historically, i'd reach for a tool like webmock / msw from ruby/js ecosystems, but I'm wondering if there's a better idiomatic JVM way to approach this problem

Do you always plan to proxy through to HTTP or will you need HTTPS?

but since https seemed like more configuration, i figured i'd try to just get http working first, then try and get https working in an example, and then move onto my actual use case haha

I suggest explicitly setting WireMock’s host/port as the HTTP client’s proxy and also telling it to trust any certificate it’s given

I’d give you the incantation to do that, but I’m about to go into a series of calls so you might need to look at Stackoverflow

ok, the library i'm using accepts http proxy port and hostname

Then if you want to do HTTPS you’ll additionally need to give it an SSL context that trusts everything

(or there’s a more complex way where you only trust our fake stuff, but that’s usually overkill)

thank you so much for your help!

I’ll look at clarifying that doc a bit

thank you so much for your help!

WireMock will only try to act as a proxy if you tell it to explicitly

So you need both WireMock and client to have it enabled

Ah, I remember why that comment is in the docs. It’s supposed to be paired with something like:

JvmProxyConfigurer.configureFor(8080);

That might also be worth a try, although again won’t work for HTTPS unless you also do the trust thing.