Question: Does the WireMock send Content-Length response header

Hello,

I need to make a response mock with a specific value of Content-Length header:

        [TestMethod]
        public async Task CheckMockHeaders() {
            var responseBody = @"<?xml version=""1.0""?><empty/>";
            mockServer
                .Given(Request
                    .Create()
                    .WithPath("/test")
                    .UsingPost())
                .RespondWith(Response
                    .Create()
                    .WithStatusCode(200)
                    .WithHeader("content-type", "text/xml")
                    .WithHeader("Content-Length", responseBody.Length.ToString())
                    .WithBody(responseBody));
            
            using (var httpClient = new HttpClient()) {
                var uri = mockServer.Urls.Single() + "test";
                using (var response = await httpClient.PostAsync(uri, new StringContent(""))) {
                    response.EnsureSuccessStatusCode();
                    Assert.IsTrue(response.Content.Headers.Any(x => x.Key == "Content-Length"));
                }
            }
        }

Unfortunately the Assert fails and the Content-Length is not part of response.Content.Headers.

I suspect problem might be in the fact that the server by default assigns header Transfer-Encoding: chunked.

According to https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Transfer-Encoding

Data is sent in a series of chunks. The Content-Length header is omitted in this case and at the beginning of each chunk you need to add the length of the current chunk in hexadecimal format…

I was not able to assign my own Transfer-Encoding: identity. I will create a separate question about it.

WireMock.Net version 1.0.3.16.

[StefH]

You are correct. I think that I switched Request en Response headers in my implementation.

I had some troubles some time ago when setting the Content-Length header on the IOwinResponse or HttpResponse object.

I will check that code again, and keep you informed.

[StefH]

Solved, see NuGet 1.0.3.18