Http Webhook Outputs does not have body content, only headers

Wosi Man 41 Reputation points
2020-07-12T04:43:42.83+00:00

Hi,

I set up the http webhook action in my logic app.
it posts the callback url to my Azure function with http trigger,
that queues a message to my other Azure function with queue trigger so I can do long running job

at the end, the queue triggered Azure function post back to the callbackUrl
the post clearly has json payload (which I logged with app insight along with response status code OK)
but in Logic Apps Http Webhook, it only shows the headers not anything in the body
it even show a special header "pubCount" I put there in the post request but nothing from the posted body content.

it's like this:
{
"headers": {
"Transfer-Encoding": "chunked",
"Host": "prod-125.westus.logic.azure.com",
"pubCount": "15",
"Request-Context": "appId=cid-v1:35980825-543f-479e-abe9-6effd9f72c59",
"Request-Id": "|0f02aa3bd52fcf4f98ec8b1249ae3533.01019e4b18689e48.",
"traceparent": "00-0f02aa3bd52fcf4f98ec8b1249ae3533-01019e4b18689e48-00",
"Content-Type": "application/json; charset=utf-8",
"Content-Length": "0"
}
}

Please let me know what I am missing in getting the final action result in the Webhook Outputs body. Thanks.

Azure Logic Apps
Azure Logic Apps
An Azure service that automates the access and use of data across clouds without writing code.
2,870 questions
{count} votes

Accepted answer
  1. Pramod Valavala 20,591 Reputation points Microsoft Employee
    2020-07-15T14:26:32.3+00:00

    Based on the discussion in this issue, looks like chunked encoding is the default and hence the behavior that you see.

    The solution would be to either set an explicit Content-Length header in your request or to use StringContent which does this for you. For example, I can confirm the following works

    await _httpClient.PostAsync(callbackUrl, new StringContent(data, Encoding.UTF8, "application/json"));
    

0 additional answers

Sort by: Most helpful