imazen / imazen/imageflow-server

Non-Image formats 404'ing using ImageFlow Server Deployed to Azure Windows App Service

Open
#95 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
C#
Stars
316
Forks
37
PR merge metrics
No merged PRs in 30d

Description

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.

Contributor guide

No contributing guide indexed for this repository

Research direction

Reproduce the ASP.NET Core 6 app using ImageFlow Dotnet Server, Azure Blob Storage, hybrid caching, and Azure Windows App Service, comparing image requests with SVG and PDF requests. Inspect the UseImageflow configuration and request path; done means existing non-image files are served instead of returning 404.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, csharp
Domain
backend, cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.