Add support for HTTPS endpoints to Azure Storage Emulator
The Azure storage emulator doesn't support HTTPS endpoints. That means that when we develop locally under SSL, we either have mixed content warnings or get broken links.
"Note that the storage emulator supports connection via HTTP only. However, HTTPS is the recommended protocol for accessing resources in an Azure production storage account."
Thank you for your feedback. Providing this functionality is on our backlog but there is no ETA we can share at this time. We have logged this request in the GitHub repository for the new open source storage emulator, Azurite. Please continue the discussion there: https://github.com/Azure/Azurite/issues/38. We will provide updates when they become available on this ask as well as in the GitHub repository. For any further questions, or to discuss your specific scenario, send us an email at firstname.lastname@example.org.
Xiaoning Liu commented
FYI. Azurite supports customized ports, OAuth and HTTPS. https://github.com/azure/azurite
Jon Gallant commented
I realize this is an old thread, but just in case you happen upon this while trying to figure out how to use Azurite with HTTPS. I created a blog post to help you setup an HTTPS -> HTTP proxy https://blog.jongallant.com/2020/02/azurite-https-defaultazurecredential/ Please comment or vote for this item if you still need HTTPS.
Girish Dasarathy commented
Is there a support for custom endpoints instead of 10000,10001,10002?
If you configure an external datasource in SQL Server to point to blob storage (for bulk inserts of data to SQL from blob) you have to specify https in the url. This means we cannot test locally as emulator only allows http
Definitely, should be able to create an https endpoint/proxy in the Azure Storage Emulator so we can test.
Maxime Rouiller commented
When downloading files, I'm using SAS to redirect the user to the blob storage.
However, since it's not HTTPS, files can't be downloaded. Chrome blocks it because of Mixed Content and security headers.
This should be added.