This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(224.00000000000003, 26%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAZ%3C/text%3E%3C/svg%3E)
Hi, we want to log request and response size for further analysis. Already studied this post to get some hint.
We use context.Request.Body.Length in the policy to get the number.
After comparing the policy logged value, APIM built-in value and Postman, we find the numbers from policy seems incorrect.
( yellow values are from policy )
Not sure why this happens, or we use wrong property ?
Need your advice, thank you
@Amy Z The postman would be having the total size (body + header). If you hover over the size you will find the body and header size.
When you use context.Request.Body.Length then it will be the request body length not the total size of the request. If you want the total size then you can add the header and body length.
@MayankBargali-MSFT thank you for the hint, I just realize hovering over the size on postman can get more information. :)
I've dumped context.Request.Headers and find Content-Length might be what I want. But it seems Content-Length is the same as context.Request.Body.Length , same result in Postman.
According to this post, it seems only body size(Content-Length) is what I can get from request/response.
@Amy Z Thanks for your response. Glad the answer helped and you were able to find the solution. Feel free to 'Accept as answer' if it helped so that it can help others in the community looking for help on similar topics.