-
-
Notifications
You must be signed in to change notification settings - Fork 204
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WireMock not working when attempting to access from anything other than localhost. #78
Comments
I'm using a dynamic ports which is hardcoding the URL to be "localhost" + port. |
Whoops didn't mean to close. I can get around this by using the PortUtil; in my calling code, so I guess its a non-issue unless you intended it to work differently? |
You could use 'https://*:80' for an url? Which makes WireMock listen on all ip? Or do you want to start WireMock with dynamic ports and listen to |
Yeah basically the second one. I just used PortUtil to get an available port and constructed a Url out of that port and a the host of the wiremock servers IP. Perhaps https://*:port would be more appropriate in the FluentMockServer. Will close though as I don't think using PortUtil directly is a "bad" thing. |
Hi there,
I've run into an issue when trying to access a wiremock mock instance running on 0.0.0.1 FROM an application running on 0.0.0.2 using https://0.0.0.1/things/other-things.
Can be replicated much simpler by trying to access a wiremock standalone instance on your local machine on your IP rather than localhost.
I'm getting a 400 Invalid Hostname.
Tried this using the java version of wiremock standalone also and it working fine.
Any ideas?
Cheers,
Josh
The text was updated successfully, but these errors were encountered: