Azure Blob Storage Metadata 400 Bad Request

rkosta profile image Ricardo Costa Originally published at blogit.create.pt on ・1 min read

I was getting a 400 Bad Request when inserting blobs in Azure Blob Storage because I was setting metadata with non-ASCII characters.

// Retrieve storage account from connection string. 
CloudStorageAccount storageAccount = CloudStorageAccount.Parse( CloudConfigurationManager.GetSetting("StorageConnectionString")); 

// Create the blob client. 
CloudBlobClient blobClient = storageAccount.CreateCloudBlobClient(); 

// Retrieve a reference to a container. 
CloudBlobContainer container = blobClient.GetContainerReference("mycontainer"); 

// Create the container if it doesn't already exist.

// Add some metadata to the container. 
container.Metadata.Add("docType", "textDocuments");

According to Microsfot documentation:

“You will receive a 400 Bad Request if any name/value pairs contain non-ASCII characters. Metadata name/value pairs are valid HTTP headers, and so must adhere to all restrictions governing HTTP headers. It is therefore recommended that you use URL encoding or Base64 encoding for names and values containing non-ASCII characters.”


The post Azure Blob Storage Metadata 400 Bad Request appeared first on Blog IT.

Posted on by:

rkosta profile

Ricardo Costa


My main focus is on Software Architecture, Enterprise Integration and Azure solutions.


markdown guide