Hello. I am running wiremock standlone in nomad ha...
# help
v
Hello. I am running wiremock standlone in nomad harshicorp and I expose it via Consul service. It seems that the java api requires me to define a port when I am creating a Wiremock instance, however this does not work with the network setup we have here, because the routing relies on the host header. How can you create an instance if you have only a dns name and the port is implied to be 443 but you dont have to specify, and certainly should not be on the path on the request?
r
if your client is implicitly connecting to port 443 then set the http(s) port to 443
v
Hey Rafe, when I do this, the http client implementation you have in the library will append the port in the path. So it will be like https://my.consul.service.wiremock.domain:443/wiremock Unfortunately, in our platform setup, we use the host header to do the routing, so the presence of the port there cannot work. All I wanted to do is the http client to call https://my.consul.service.wiremock.domain/wiremock After all, if I try to do the stubbing through POSTMAN, I can do it without passing the :443 in the path, so it seems to be a limitation of the library
r
i see the issue. this does appear to be a limitation of the library. raising an issue, or better yet, a pr is the best way for the feature to be added to WireMock.
v
Let me know when you have a look
h
@Rafe Arnold - @Vangelis Georgas is now on Paternity leave for the next few months, and I will be taking over for him for this PR. Please let me know if you need anything. Also can you give me an ETA on how long an approved PR gets merged and into the next iteration of the public project.
r
ive left a request on the pr. other than that, it looks good
h
Hi @Rafe Arnold, I have updated the PR reflecting your comments.