com.azure.storage.blob.models.BlobStorageException: Status code 400, (empty body)

Which service(blob, file, queue, table) does this issue concern?

blob

Which version of the Azurite was used?

3.7.0 (mcr.microsoft.com/azure-storage/azurite:3.7.0) I also used azurite:latest.

Where do you get Azurite? (npm, DockerHub, NuGet, Visual Studio Code Extension)

DockerHub

What’s the Node.js version?

na (FROM node:10-alpine in Dockerfile)

What problem was encountered?

When using com.azure:azure-storage-blob:12.6.1 and using listBlobs an exception is thrown: com.azure.storage.blob.models.BlobStorageException: Status code 400, (empty body)

^ this is inconsistent with the production Azure blob storage service. This issue is documented here: https://github.com/Azure/azure-sdk-for-java/issues/6945. Azurite should have the same behaviour as the production service.

Steps to reproduce the issue?

//String connectionString = realConnectionString;
String connectionString = fakeConnectionString;
System.out.println("Using the Connection String: " + connectionString);

String containerName = "somecontainer";
StorageSharedKeyCredential credential = StorageSharedKeyCredential.fromConnectionString(connectionString);

BlobContainerClient blobContainerClient = new BlobContainerClientBuilder()
         .connectionString(connectionString)
         .containerName(containerName)
        .credential(credential)
        .buildClient();

// create the container if it doesn't already exist
if (!blobContainerClient.exists()) {
    blobContainerClient.create();
}

String location = "testing";

// As documented by https://github.com/Azure/azure-sdk-for-java/issues/6945
ListBlobsOptions options = new ListBlobsOptions().setDetails(new BlobListDetails().setRetrieveMetadata(true));

// this passes ✅
//PagedIterable<BlobItem> blobs = blobContainerClient.listBlobsByHierarchy(location, options, Duration.ofSeconds(15));
// this fails ❌
PagedIterable<BlobItem> blobs = blobContainerClient.listBlobsByHierarchy(location);
        assertFalse(blobs.iterator().hasNext());

Have you found a mitigation/solution?

ListBlobsOptions options = new ListBlobsOptions().setDetails(new BlobListDetails().setRetrieveMetadata(true));
blobContainerClient.listBlobsByHierarchy(location, options, Duration.ofSeconds(15));

[XiaoningLiu]

It’s another undocumented behavior for Azure Storage production, not an issue of Azurite.

[blueww]

@snodnipper

Thanks for the info! I get the failure happens when “include=” don’t have any value. As I see, Java SDK has fixed the issue, and I don’t see other SDK (like .net) has this issue. So seems the issue is not blocking currently.

We will discuss how to fix it, and update when get a decision.