Can not use Front Door URL for blob storage account in BlobServiceClient for React App

• Package Name: @azure/storage-blob
• Package Version: 12.2.0-preview.1
• Operating system:
• nodejs
  • version:
• browser
  • name/version: Google Chrome/Version 84.0.4147.105 (Official Build) (64-bit)
• typescript
  • version: 3.9.6
• Is the bug related to documentation in
  • README.md
  • source code documentation
  • SDK API docs on https://docs.microsoft.com

Describe the bug We have an Azure Blob Storage Account running behind Azure Front Door to provide custom URL & improve traffic performance. The react app ( scaffold from CRA), uses the @azure/storage-blob for upload, download, list & delete operations using SASToken. The App runs fine when running with Blob URL example - https://example.blob.core.windows.net appended with SASToken. However when it is replaced with Front Door custom URL, BlobServiceClient fails with error :

Error: Unable to extract accountName with provided information.
    at getAccountNameFromUrl (utils.common.ts:556)
    at BlobServiceClient.StorageClient (StorageClient.ts:79)
    at new BlobServiceClient (BlobServiceClient.ts:444)
    at BlobStorageService.init (BlobStorageService.ts:35)

To Reproduce Steps to reproduce the behavior:

1. Create a Front Door entry for Blob Storage Account URL.
2. Try to create BlobServiceClient as

const customFrontDoorURL = 'https://files.xyz.com';
const blobServiceClient = new BlobServiceClient(`${customFrontDoorURL}/${SASToken}`);

Expected behavior A valid service client is created.

[jiacfan]

Hi, @pritesha

Custom domain support has been released with @azure/storage-blob 12.2.0, welcome to have a try.

Thanks, Jiachen

[jeremymeng]

My proposal here is to remove the accountName parsing error in both places considering accountName is not essential for all scenarios. and we can leave accountName as empty (or undefined with breaking change to make the variable nullable) if it’s e.g. in custom domain scenario, @jeremymeng @XiaoningLiu what’s your ideas?

Sorry I misread this part and thought about removing accountName. Yes I like this approach: removing validation of accountName and leave it empty in the case where it is not available.

By the time this bug is fixed & released, is there any workaround ?

@pritesha other than patching our code manually I don’t know an easy workaround.