Naming Containers, Blobs, and Metadata

The container name must be a valid DNS name, conforming to the following naming rules:

1. Container names must start with a letter or number, and can contain only letters, numbers, and the dash (-) character.
   
   
2. Every dash (-) character must be immediately preceded and followed by a letter or number; consecutive dashes are not permitted in container names.
   
   
3. All letters in a container name must be lowercase.
   
   
4. Container names must be from 3 through 63 characters long.
   
   

A blob name can contain any combination of characters, but reserved URL characters must be properly escaped. A blob name must be at least one character long and cannot be more than 1,024 characters long.

참고

Avoid blob names that end with a dot (.), a forward slash (/), or a sequence or combination of the two. The URL that identifies a blob is constructed with the .NET Uri class, which compacts a URL that ends with these sequences. A blob with a name that contains such a sequence may not be accessible via its original name. For example, if you specify a blob name of myBlob. on the URL, the Blob service will read the blob name as myBlob, because the .NET URI class trims the trailing dot (.). For this reason, these types of names should be avoided.

The Blob service is based on a flat storage scheme, not a hierarchical scheme. However, you may specify a delimiter within a blob name to create a virtual hierarchy. For example, the following are all valid and unique blob names:

• /a
  
  
• /a.txt
  
  
• /a/b
  
  
• /a/b.txt
  
  

You can take advantage of the delimiter character when enumerating blobs. By specifying the delimiter character in the delimiter parameter of the List Blobs operation, you can limit the list to blobs with the same name preceding the delimiter, effectively limiting the results to a virtual node.

Metadata for a container or blob resource is stored as a name-value pair associated with the resource. Beginning with version 2009-09-19, metadata names must adhere to the naming rules for C# identifiers.

Existing metadata names that do not adhere to these naming rules can be used with earlier versions of the Blob service, but not with version 2009-09-19 or later.

Note that metadata names preserve the case with which they were created, but are case-insensitive when set or read. If two or more metadata headers with the same name are submitted for a resource, the Blob service returns status code 400 (Bad Request).