req.Content.ReadAs<T> fails to deserialize when using WebHook SDK auth

Use a WebHook with this code:

using System;
using System.Net;
using System.Threading.Tasks;

public static async Task<object> Run(HttpRequestMessage req, TraceWriter log)
{
    var foo = await req.Content.ReadAsAsync<Foo>();
    return req.CreateResponse(HttpStatusCode.OK, $"foo is null: {foo==null}");
}

class Foo {}

If I pass the request body {} from our Functions test UI, it works fine. i.e. foo is not null.

But if I try to do the same thing from postman, passing the same body {} as application/json, then I end up with foo=null.

If It set the x-functions-key header to the master key in postman (to do the same as Function Portal, instead of using code query string), then it works! So I suspect some issue from the WebHook SDK auth messing up the state of the request.

[mathewc]

Also, I had Pizza for dinner. @paulbatum @fabiocav

[mathewc]

Yeah, I’d like to know the root cause too - to be sure it isn’t something we’re doing wrong. I think it only happens when going through the WebHook receiver pipeline because those libraries are also reading the content, so there are multiple readers.

It’d be interesting to try to reproduce this issue using the WebHook receiver libraries outside of functions, to truly find out if it’s something we’re doing wrong, or whether Henrik has a bug.