-
Notifications
You must be signed in to change notification settings - Fork 66
Closed
Description
If you are using this package and have the Virtual Path Provider configured, and you have a page at the root of your Umbraco site called "Media" (/media/), you will receive this exception when trying to visit the page:
System.ArgumentException: The argument must not be empty string.
Parameter name: blobName
at Microsoft.WindowsAzure.Storage.Core.Util.CommonUtility.AssertNotNullOrEmpty(String paramName, String value)
at Microsoft.WindowsAzure.Storage.Blob.CloudBlobContainer.GetBlockBlobReference(String blobName, Nullable`1 snapshotTime)
at Microsoft.WindowsAzure.Storage.Blob.CloudBlobContainer.GetBlockBlobReference(String blobName)
at Our.Umbraco.FileSystemProviders.Azure.AzureFileSystem.GetBlockBlobReference(String path) in J:\Dev\Projects\UmbracoFileSystemProviders.Azure\src\UmbracoFileSystemProviders.Azure\AzureFileSystem.cs:line 526
at Our.Umbraco.FileSystemProviders.Azure.AzureFileSystem.FileExists(String path) in J:\Dev\Projects\UmbracoFileSystemProviders.Azure\src\UmbracoFileSystemProviders.Azure\AzureFileSystem.cs:line 330
at Our.Umbraco.FileSystemProviders.Azure.AzureBlobFileSystem.FileExists(String path) in J:\Dev\Projects\UmbracoFileSystemProviders.Azure\src\UmbracoFileSystemProviders.Azure\AzureBlobFileSystem.cs:line 132
at Our.Umbraco.FileSystemProviders.Azure.FileSystemVirtualPathProvider.FileExists(String virtualPath) in J:\Dev\Projects\UmbracoFileSystemProviders.Azure\src\UmbracoFileSystemProviders.Azure\FileSystemVirtualPathProvider.cs:line 125
at System.Web.Routing.RouteCollection.IsRouteToExistingFile(HttpContextBase httpContext)
at System.Web.Routing.RouteCollection.GetRouteData(HttpContextBase httpContext)
at System.Web.Routing.UrlRoutingModule.PostResolveRequestCache(HttpContextBase context)
at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
I'm assuming this is some conflict with the VirtualPathProvider, but I'm not quite sure what the fix would be (if any). Could it perhaps ignore itself and only kick in for requests beneath it? (ie /media/*)
Metadata
Metadata
Assignees
Labels
No labels