This issue occurs when an Azure Blob Storage blob does not serve a content-disposition header, despite being set to "inline; filename=bispham+gala.jpg". This is observed through the Azure UI. The problem can arise due to several reasons, including misconfiguration or a potential bug in Blob Storage.
To resolve this issue, first ensure that the content-disposition header is correctly set for the specific blob. This can be verified through Azure Storage Explorer or by using Azure CLI commands. If the configuration is correct and the issue persists, it may be necessary to consult Azure Support or check the Azure Blob Storage documentation for any recent updates or known issues.
For further assistance, follow these steps: 1. Verify the blob's properties using Azure Storage Explorer or Azure CLI. 2. Ensure the content-disposition header is set correctly. 3. Check for any updates or known issues in the Azure Blob Storage documentation. 4. If the problem persists, contact Azure Support for further investigation.
Resources:
- Azure Blob Storage documentation
- Set Blob Properties using Azure Storage Explorer
- Azure CLI Reference for Blob Storage
Hope this helps. If you have any follow-up questions, please let me know. I would be happy to help.
Please do not forget to "Accept the answer" and "up-vote" wherever the information provided helps you, as this can be beneficial to other community members.