Fails to read response content twice about mockhttp HOT 4 CLOSED

This has been resolved in v1.3.1, now available on NuGet.

from mockhttp.

If I change to this

mockHandler
  .When("/test")
  .Respond(HttpStatusCode.OK, new ObjectContent<ResponseDto>(new ResponseDto("OK"), new JsonMediaTypeFormatter()));

Then response content is not null the second time. But it would be good if the json string would work because that's the format I have in my expected payloads. I would like to avoid creating the Dtos before the mocks.

from mockhttp.

Hi Martin,

This is actually a limitation with how ReadAsAsync<T> uses HttpContent, and has nothing to do with MockHttp.

HttpContentExtensions.ReadAsAsync<T> calls HttpContent.ReadAsStreamAsync, which reuses the existing memory buffer without resetting it's position, which causes ReadAsAsync<T> to return null since it thinks there's no data.

There's not much point attempting to workaroud this in my opinion, so I'd advise simply limiting your application to only call ReadAsAsync<T> once.

Cheers,
Richard

from mockhttp.

It just occurred to me that you are actually making the request twice, so the real HttpClient would actually send back two different responses. This is definitely a bug in MockHttp's behavior. Thanks for bringing it to my attention.

I'll look at fixing this behavior, but in the meantime you can workaround it by using a different Respond overload that creates a new HttpConent each time:

mockHandler
    .When("/test")
    .Respond(req => new HttpResponseMessage(HttpStatusCode.OK)
    {
        Content = new StringContent("{'Status' : 'OK'}", Encoding.UTF8, "application/json")
    });

from mockhttp.