This issue is happening specifically when the initial HTTP GET request includes the “Range” header as discussed at https://learn.microsoft.com/en-us/azure/logic-apps/logic-apps-handle-large-messages#download-content-in-chunks .
I have confirmed via Postman that the endpoint accessed (Azure Blob Storage) does respond to Range requests.
The issue is that it doesn’t seem like the HTTP action is sending this Header in the GET as the entire dataset is being returned regardless of the Range submitted. In addition, though in most cases using the HTTP action return/display the Headers in the response, it is not in this particular scenario.
Flow screenshot:
Post-Run screenshot. No Headers returned. As an extreme example, did a range of 0-1 and the $content is obviously more than a 2 bytes.
Hi @hmclean_blkb,
It is not mentioned as one of the Headers which are omitted/ignored by the HTTP action, according to this doc:
https://learn.microsoft.com/en-us/azure/connectors/connectors-native-http#omitted-http-headers
However, my suggestion would be to still double check with Microsoft support if you want to keep using the HTTP action.
Alternatively, have you tried creating/using a Custom connector? That gives you a lot more options.
Michael E. Gernaey
566
Super User 2025 Season 1
David_MA
516
Super User 2025 Season 1
stampcoin
492