In the portal I want to be able to set (or at least see) http headers like "Cache-Control" at blob containers. We had an issue with CDN not caching images from blob when Cache-Control was not set to public.
Imre Pühvel commented
Current Cache-Control headers per blob are really cumbersome to change should application caching needs and policies change (and they do). In my project I have never needed to tailor caching for individual blobs, but to apply the same policy to ALL blobs of a similar meaning. Such blobs are usually organized into same containers/accounts. It seems like a common need.
Current solution to enumerate all blobs in all containers and change their Cache-Control header would require custom scripting every time. Should you have millions of blobs this takes a lot of operations to bounce between Azure Storage and client. Getting overview and verification of Cache-Control settings once again requires another one-by-one enumeration of those millions of blobs.
I acknowledge that per-blob granularity can be useful for many scenarios but I suggest a fallback to be implemented where the first existing Cache-control header is passed by examining:
Temporary workaround could be if Azure Storage Explorer would provide a tested and optimized command to apply a new Cache-Control header to all blobs in blob container .