imazen
Non-Image formats 404'ing using ImageFlow Server Deployed to Azure Windows App Service
We have a aspnetcore 6 web app using ImageFlow Dotnet Server deployed as a windows app service to serve files and resize images from azure blob storage. Also have hybrid caching implemented. It works well enough for image files(.jpg, .png) but any non-image format, e.g, SVG, PDF, 404s. These files definitely exist in blob storage. Is there some configuration that must be set in, say, app.UseImageflow to enable all files to be served. It definitely is not a MIME type issue with the app service. The static web server can serve these files up.
Are you sure you want to relay the unmodified files via the disk cache? It's not adding any benefit except sharing a dns address. I could add this feature to a future release.
On Mon, Jun 3, 2024, 12:18 AM S. Francis @.***> wrote:
We have a aspnetcore 6 web app using ImageFlow Dotnet Server deployed as a windows app service to serve files and resize images from azure blob storage. Also have hybrid caching implemented. It works well enough for image files(.jpg, .png) but any non-image format, e.g, SVG, PDF, 404s. These files definitely exist in blob storage. Is there some configuration that must be set in, say, cs app.UseImageflow to enable all files to be served. It definitely is not a MIME type issue with the app service. The static web server can serve these files up.
— Reply to this email directly, view it on GitHub https://github.com/imazen/imageflow-dotnet-server/issues/95, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAA2LH62IESTFIQ6JOKW2ADZFP4D5AVCNFSM6AAAAABIVYFP6KVHI2DSMVQWIX3LMV43ASLTON2WKOZSGMZTAMJZGQ4TQOA . You are receiving this because you are subscribed to this thread.Message ID: @.***>
I'm not clear with your response. I assume the hybrid caching is used to cache image jobs, not unmodified pass throughs. In any event, the original issue is with the 404 for all non image formats. That's what I'm trying to resolve at the moment.