Blob storage API should be case insensitive, like NTFS
I wrote an IFileSystem implementation that uses a blob container as backing storage. Unfortunately I found that the api to be case sensitive, which makes it difficult and less performant to write.
According to http://www.deveducate.com/blog/post/2010/11/23/Azure-Blob-URIs-are-case-sensitivee28093just-ask-your-shrink.aspx this is because it is consistent with rest apis.
Whatever standards may state, since blob storage is a hierarchical path-->contents system, it should behave like other such systems (NTFS) and return the blob regardless of the casing of the path from the container.
For now, the workaround for me is to always lowercase (http://social.msdn.microsoft.com/Forums/windowsazure/en-US/24cc9b63-6781-4371-b2ee-89067ffda381/is-there-a-way-to-remove-the-case-sensitivity-from-blob-storage?forum=windowsazuredata), but this means my filesystem can not be reused in contexts where the consumer needs to preserve casing when enumerating files.
Thank you for your feedback. Unfortunately, we do not plan to add this feature to our platform at this time. Using the Azure Files service you can address Azure Storage like a network share using the SMB2.1 protocol. This enables usage of normal Windows API’s to rename files and directories. You can get started with the Files service by visiting https://docs.microsoft.com/en-us/azure/storage/storage-dotnet-how-to-use-files. We will provide an update if the status of this ask changes. For any further questions, or to discuss your specific scenario, send us an email at email@example.com.
Ivan Dimitrov commented
It's a pain if you're using this as origin for your CDN service. It's basically useless.
Ravi Sabharanjak commented
Having a case insensitive access option also makes sense if you are using the static website feature of the storage blob
Jonas Stawski commented
why not add an opt in option to the rest api to make it case insensitive?