Public media/blob URLs fail after upgrading EPiCode.SqlBlobProvider from 2.0.0 to 2.1.0

[HeineMo]

After upgrading from 2.0.0 to 2.1.0, public media URLs under /globalassets/... stop loading on our Optimizely CMS 12 site (.NET8, IIS hosting).

We are using:

"SqlBlobProvider": {
"LoadFromDisk": true
}

The relevant log entry is:

System.InvalidOperationException: The response cannot be cleared, it has already started sending.
at Microsoft.AspNetCore.Http.ResponseExtensions.Clear(HttpResponse response)
at Microsoft.AspNetCore.StaticFiles.StaticFileContext.ServeStaticFile(HttpContext context, RequestDelegate next)
at EPiServer.Web.Routing.Matching.Blobs.Internal.DefaultBlobHttpHandler.Invoke(HttpContext context)
at EPiServer.Cms.Shell.UI.Controllers.Preview.Internal.MediaEditRenderer.InvokeAsync(HttpContext context)

Looking at commit 6c0e45e, I see that 2.1.0 adds AsFileInfoAsync(DateTimeOffset?) and returns an IFileInfo implementation with Exists, Length, PhysicalPath, and CreateReadStream(). Since our failing stack goes through StaticFileContext.ServeStaticFile, I wonder if this new IFileInfo behavior could affect how Optimizely/ASP.NET Core serves SQL-backed blobs when LoadFromDisk = true.

Are there any known issues or required configuration changes in 2.1.0 when using LoadFromDisk = true?

[LucGosso]

Hi @HeineMo we do run with path too? dont you have a path?

      "SqlBlobProvider": {
        "LoadFromDisk": true,
        "Path": "c:\\temp\\local_optimizely_cache"
      }

without path, the provider should throw an error... ?

[LucGosso]

try if you get same error with 2.1.1

[HeineMo]

Hi @HeineMo we do run with path too? dont you have a path?

      "SqlBlobProvider": {
        "LoadFromDisk": true,
        "Path": "c:\\temp\\local_optimizely_cache"
      }

without path, the provider should throw an error... ?

No, the description states the following:
"If you do not specify the Path property, it will default to [appDataPath]\sqlProviderBlobs"
And it worked without path and did as described. I will try again with 2.1.1