[BUG] Support non-IP address based development URLs

Describe the bug

Since migrating to version 12 of the SDK it will no longer connect to Azurite in a docker container.

Exception or Stack Trace

dm-store_1                        | 2020-02-03 13:51:19.946 ERROR 1 --- [nio-8080-exec-2] u.g.h.d.errorhandler.ApiErrorAttributes  : Status code 501, "Path or Http-Method does not match any emulated command.
dm-store_1                        | Possible causes include
dm-store_1                        |   - missing account name path parameter
dm-store_1                        |   - Unsupported Http-Method on resource
dm-store_1                        |   - Unsupported / Not implemented "comp" query parameter on resource"

To Reproduce

Create a docker compose file with Azurite and try to access it using it’s container name.

For example: https://github.com/hmcts/rpa-em-ccd-orchestrator/blob/master/docker-compose-dependencies.yml#L152-L202

Code Snippet

This is the change that causes the problem:

https://github.com/Azure/azure-sdk-for-java/pull/6156/files#diff-c498bc9cb41a9cfda139edbe2bd692c9R105-R110

Expected behavior

It should be possible to use Azurite with a non-IP address connection string.

Screenshots

N/A

Setup (please complete the following information):

• OS: Ubuntu 18.04
• IDE : IntelliJ
• Version of the Library used: 12.3.0

Additional context

Relates to #6140

Information Checklist Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

• Bug Description Added
• Repro Steps Added
• Setup information Added

[linusnorton]

Not quite, I am trying to use http://azure-storage-emulator-azurite:10000/devstoreaccount1 as part of a docker compose file that uses the Azurite container: https://hub.docker.com/_/microsoft-azure-storage-azurite.

It uses to work with version 8 but stopped when I upgraded to 12.2.0. Using 12.3.0 didn’t help either.

[JonathanGiles]

Thanks for using our Azure SDK and reporting this issue. @rickle-msft will take a closer look at this issue and get back to you.