Blob Storage Not Serving Content-Disposition Header

Question

Why does my Azure Blob Storage not serve a content-disposition header even though it is set to inline?

 "PS - Based on common issues that we have seen from customers and other sources, we are posting these questions to help the Azure community."

Answer 1

Hi Abdul - Thanks for reaching out over Q&A forum.

Based on verbatim, I could learn that even though the disposition header is set as inline, the content gets downloaded and not showed inline? Is that understanding correct?

This can also be affected by the default storage service version as well. DefaultServiceVersion indicates the default version to use for requests to the Blob service if an incoming request’s version is not specified.

In case you are working with SAS, the service version gets picked from the version parameter however in your case you seem to be not passing that, the version gets picked from the account one and if it is older, it might tend to behave differently. This should be a good isolation test.

Further, you can try setting the Storage Account Default Service version using below REST API Set Blob Service Properties (REST API) - Azure Storage | Microsoft Docs to a more recent one and observe the behavior ahead. However, using this option in case you are making any other operations which is not supported on the default version that might get failed.

Hope that helps!

Please let me know if there are any further queries/concerns, will be glad to assist.

---

Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.