Is there an existing issue for this?

• I have searched the existing issues

What happened?

We enabled the built-in Azure Storage connector, then connected it to an Azure blog storage location. After synchronizing the files, the resulting links in the Resource Manager are prepended with the portal alias. These URLs are already fully qualified URLs.

Steps to reproduce?

1. Install latest version of DNN.
2. Create and configure an Azure Blob storage container with appropriate API keys.
3. Connect the Azure Storage connector in DNN to the Azure Blob.
4. Go to the Resource Manager and choose to synchronize the folders.

Current Behavior

THe folders appear, but clicking on a file to see the URL will yield a surprising result. The URLs for all cloud files have the portal alias prepended to it, creating a bad link.

The URL looks something like this:

https://www.example.comhttps//BLOBLNAME.blob.core.windows.net/FOLDERNAME/FILENAME.png?sv=2023-08-25&sr=b&si=DNNFileManagerPolicy&sig=53MzIMXOjSVgjwYcqYECZet%2Fxh%2F%2WIWWH%2Fue0ja7HD073A%3D

Expected Behavior

The generated URL is correct and can be used.

The actual URL should be this:

https//BLOBLNAME.blob.core.windows.net/FOLDERNAME/FILENAME.png?sv=2023-08-25&sr=b&si=DNNFileManagerPolicy&sig=53MzIMXOjSVgjwYcqYECZet%2Fxh%2F%2WIWWH%2Fue0ja7HD073A%3D

Relevant log output

N/A

Anything else?

No response

Affected Versions

9.12.0 (latest release)

What browsers are you seeing the problem on?

Firefox, Chrome, Safari, Microsoft Edge

Code of Conduct

• I agree to follow this project's Code of Conduct