-
-
Notifications
You must be signed in to change notification settings - Fork 213
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
Port where WireMockServer listens to - v1.2x #445
Comments
Do you use .NET Framework version ? Or .NET Core ? And can you provide the start command you use? |
This seems a bug, I've to investigate more. As a workaround you can provide the |
I am using .NET Core 2.2 I tried these 2 methods:
|
You can try preview NuGet : WireMock.Net.1.2.1-ci-13017 |
Hi @StefH , thanks for the prompt replies : ) I still don't see the WireMock.Net.1.2.1-ci-13017 prerelease package available. I confirm that specifying the URL including the port does work. |
uh sorry...I missed that. Yup, the issue looks fixed in here: WireMock.Net.1.2.1-ci-13017 👍 I tested again with the prerelease package WireMock.Net.1.2.1-ci-13017 and it work just specifying the port either with:
|
OK. Closing issue, a new 1.2.2 version will be uploaded to normal NuGet in some time... |
Hello, since version 1.2.0 it looks like the WireMockServer starts listening on a random port instead of the one specified in the settings.
it seems the issue happens with all the different .Start overload methods.
The text was updated successfully, but these errors were encountered: