Ability to define cache-control property
See original GitHub issueFeature Request Description
Based on the documentation it is possible to define cache-control property when uploading a blob:
https://docs.microsoft.com/en-us/azure/cdn/cdn-manage-expiration-of-blob-content
azure storage blob upload -c <connectionstring> -p cacheControl="max-age=3600" .\<blob name> <container name> <blob name>
Such functionality is missing from blobxfer
.
Describe Preferred Solution
Would you consider adding --cache-control "max-age=3600"
option to the command line interface?
Issue Analytics
- State:
- Created 5 years ago
- Comments:7
Top Results From Across the Web
What is cache-control? | Cache explained
Cache control dictates caching behavior for a website, letting browsers know how often to refresh locally stored resources.
Read more >Cache-Control - HTTP - MDN Web Docs
The Cache-Control HTTP header field holds directives (instructions) — in both requests and responses — that control caching in browsers and ...
Read more >Set cache-control to Azure blob storage items
In one of my customer's application, we are storing static content (such as icons, and logos) in an Azure Storage Account blob container....
Read more >Caching
How it works. Default settings apply to all objects under your property configuration. For example, the caching setting tells the edge servers to...
Read more >Understanding caching
WebSphere Voice Server supports these directives in accordance with HTTP 1.1. Briefly defined, max-age permits a client the ability to restrict the age...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I checked now again and magically the header was there. Not sure, maybe it was a cache issue, but I swear I hard reloaded. Sorry for confusion and thanks for your work on this! 😃
If you search your gist for
x-ms-blob-cache-control
, the correct value is being sent/set. Are you positive you aren’t seeing theCacheControl
blob property on the associated blobs if viewed in Azure Storage Explorer?