An error '403 Server failed to authenticate the request.' shows when executing 'Download All...' for one docker container/custom account

[v-kellyluo]

Storage Explorer Version

1.38.0-dev (104)

Regression From

Not a regression

Architecture

x64

Storage Explorer Build Number

20250311.3

Platform

All

OS Version

Windows11 x64/Windows 11 arm64/Linux Ubuntu 22.04/MacOS Sequoia 15.0(Apple M1 Pro)

Bug Description

An error '403 Server failed to authenticate the request' shows when executing 'Download All...' for one docker container/custom account.

Steps to Reproduce

1. Install Docker desktop.
2. Run docker –version to make sure docker is installed successfully.
3. Run Azurite with docker with the following command:
   docker run -p 10000:10000 -p 10001:10001 -p 10002:10002 \ -e AZURITE_ACCOUNTS="customaccount1:Eby8vdM02xNOcqFlqUwJPLlmEtlCDXJ1OUzFT50uSRZ6IFsuFq2UVErCz4I6tq/K1SZFPTOtr/KBHBeksoGMGw==" \ --name azurite-container mcr.microsoft.com/azure-storage/azurite
4. Open Storage Explorer -> Expand the custom account.
5. Blob Containers -> Create a blob container.
6. Upload a blob -> Click 'Download -> Download All...'.
7. Check whether the downloaded items are transferred successfully.

Actual Experience

An error '403 Server failed to authenticate the request.' shows in the activity log.

Error details:Server failed to authenticate the request. Make sure the value of the Authorization header is formed correctly including the signature.

Expected Experience

The downloaded items are transferred successfully.

Additional Context

This issue doesn't reproduce for emulator blob containers.

[craxal]

I tried this using the Default Ports connection, and it worked. The only difference I could see between the Default Ports and the Docker container connections was the use of "127.0.0.1" vs "localhost". And when I changed the Docker connection to use "127.0.0.1", it started working.

The seems like a bug in Azurite, but we can adjust our code to use 127.0.0.1.

Azure/Azurite#2538