starred/WireMock.Net-wiremock
1
0
Fork 0
mirror of https://github.com/wiremock/WireMock.Net.git synced 2026-07-31 01:08:41 +02:00
Code Issues 32 Packages Projects Releases 10 Wiki Activity

WireMock Server does not appear to function correctly with Microsoft.Extensions v3.1 #240

New Issue
Closed
opened 2025-12-29 15:18:56 +01:00 by adam · 4 comments
adam commented 2025-12-29 15:18:56 +01:00
Owner
Copy Link
Copy Source

Originally created by @dalmuti509 on GitHub (Dec 23, 2019).

If project nuget packages are updated to include Microsoft.Extensions v3.1 nuget libraries, the WireMock server seems to stop correctly responding to requests as all responses result in an invalid format status code 0 when responses are received from HttpClient.

Simple repro which returns 0 after an extended timeout:

            Server.Given(
               Request.Create()
                   .WithPath($"*")
                   .UsingGet()
             )
             .RespondWith(
               Response.Create()
                 .WithStatusCode(HttpStatusCode.OK)
                 .WithBody("{}")
             );

            HttpClient client = new HttpClient();
            var result = client.GetAsync(Server.Urls.First()).Result;
            result.StatusCode.Should().Be(HttpStatusCode.OK);  //Use FluentAssertions

This can be run on line 14 at: WireMock.Net/examples/WireMock.Net.StandAlone.Net461/Program.cs

Update the project to the latest nugets to see the failure.

Originally created by @dalmuti509 on GitHub (Dec 23, 2019). If project nuget packages are updated to include Microsoft.Extensions v3.1 nuget libraries, the WireMock server seems to stop correctly responding to requests as all responses result in an invalid format status code 0 when responses are received from HttpClient. Simple repro which returns 0 after an extended timeout: ``` Server.Given( Request.Create() .WithPath($"*") .UsingGet() ) .RespondWith( Response.Create() .WithStatusCode(HttpStatusCode.OK) .WithBody("{}") ); HttpClient client = new HttpClient(); var result = client.GetAsync(Server.Urls.First()).Result; result.StatusCode.Should().Be(HttpStatusCode.OK); //Use FluentAssertions ``` This can be run on line 14 at: WireMock.Net/examples/WireMock.Net.StandAlone.Net461/Program.cs Update the project to the latest nugets to see the failure.
adam added the question label 2025-12-29 15:18:56 +01:00
adam closed this issue 2025-12-29 15:18:56 +01:00
adam commented 2025-12-29 15:18:56 +01:00
Author
Owner
Copy Link
Copy Source

@jlobec commented on GitHub (Feb 20, 2020):

Should an "await" be used instead of ."Result" when getting the HttpClient response on this snippet? AFAIK the .Result is only correct if you're absolutely sure that the task is already completed (which I'm afraid is not the case) and could cause deadlocks
Maybe not directly related with the issue topic but will save time in the future :)

@jlobec commented on GitHub (Feb 20, 2020): Should an "await" be used instead of ."Result" when getting the HttpClient response on this snippet? AFAIK the .Result is only correct if you're absolutely sure that the task is already completed (which I'm afraid is not the case) and could cause deadlocks Maybe not directly related with the issue topic but will save time in the future :)
adam commented 2025-12-29 15:18:57 +01:00
Author
Owner
Copy Link
Copy Source

@StefH commented on GitHub (Feb 20, 2020):

Could be.
Better code should be '.GetAwaiter().GetResult()' I think.

@StefH commented on GitHub (Feb 20, 2020): Could be. Better code should be '.GetAwaiter().GetResult()' I think.
adam commented 2025-12-29 15:18:57 +01:00
Author
Owner
Copy Link
Copy Source

@NoahLerner commented on GitHub (Feb 22, 2020):

Could be.
Better code should be '.GetAwaiter().GetResult()' I think.

Looks to me like best practice is using async await as apposed to GetAwaiter. Microsoft documentation indicates that GetAwaiter is not intended to be used in application code.

@NoahLerner commented on GitHub (Feb 22, 2020): > Could be. > Better code should be '.GetAwaiter().GetResult()' I think. Looks to me like best practice is using `async await` as apposed to `GetAwaiter`. Microsoft documentation indicates that `GetAwaiter` is not intended to be used in application code.
adam commented 2025-12-29 15:18:57 +01:00
Author
Owner
Copy Link
Copy Source

@StefH commented on GitHub (Apr 3, 2020):

closing..

@StefH commented on GitHub (Apr 3, 2020): closing..
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
doc
doc
duplicate
feature
feature
invalid
pull-request
Mirrored from GitHub Pull Request
 question
wontfix
No labels question
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Melkus)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/WireMock.Net-wiremock#240