Stubbed response with only callback returns unexpected status code.

Describe the bug

When setting up a stubbed response with only a callback I would expect that the status code which I set on the returned ResponseMessage would be the status code which the request will receive. But you always get HttpStatusCode.OK anyway.

Expected behavior:

If I only specify .WithCallback() and not .WithStatusCode() I would expect that the status code of the returned ResponseMessage object is returned.

Test to reproduce

This test is currently failing with WireMock.Net 1.3.5

using System.Net;
using System.Net.Http;
using System.Threading.Tasks;
using NUnit.Framework;
using WireMock;
using WireMock.RequestBuilders;
using WireMock.ResponseBuilders;
using WireMock.Server;

namespace WireMockIssue
{
    [TestFixture]
    public class StatusCodeStubIssue
    {
        private WireMockServer _mockServer;

        [SetUp]
        public void Setup()
        {
            _mockServer = WireMockServer.Start(8088);
            _mockServer
                .Given(Request.Create().WithPath("/foo"))
                .RespondWith(Response.Create()
                    .WithCallback(request => new ResponseMessage {StatusCode = HttpStatusCode.Conflict}));
        }

        [TearDown]
        public void TearDown()
        {
            _mockServer.Dispose();
        }

        [Test]
        public async Task TestToGetHttpConflictStatus()
        {
            using var httpClient = new HttpClient();
            var response = await httpClient.PostAsync("http://localhost:8088/foo", new StringContent("dummy"));
            Assert.That(response.StatusCode, Is.EqualTo(HttpStatusCode.Conflict));
        }
    }
}

It fails with:

WireMockIssue.StatusCodeStubIssue.TestToGetHttpConflictStatus

  Expected: Conflict
  But was:  OK

Other related info

I checked in the debugger that the callback was triggered. It was triggered.

[StefH]

See https://github.com/WireMock-Net/WireMock.Net/wiki/MyGet-preview-versions

[StefH]

Hello @rudi-brunner, thank you for finding this bug. I’ll take a look.