Currently Web.Headers only returns generic response headers. Most APIs return paging information(count, start,end) in response headers. Exposing custom response headers would significantly speed up ...
+1 on this. The Shopify REST api, for example, sends back pagination information in the header. Since it is filtered out but needed, you have to develop a custom connector, which then requires a Gateway.
If the response headers were available, this could all be done without need of a connector.
