[FEATURE] Allow to ignore non-image files (pdf, webm, mp4, mp3, etc.)

[Vadorequest]

Is your feature request related to a problem? Please describe.
I want to use the CDN as a multi-purpose CDN, I wish it would behave differently when loading a PDF file, for instance

https://cdn.the-funding-place.unly.org/exe-v4/ece-v4-flyer-partenariat-caisse-depargne455.pdf will show an error, but I'd like to prompt a download instead.

It doesn't really make sense to use multiple CDN for different file types, it makes things more complex to manage.
So, I believe we should have a way to make the app behave differently depending on the file being manipulated.

The most logical choice would be that any type that isn't handled would prompt a download, I don't think we need more than that at this time, it'd be a good default behavior.

Describe the feature you'd like
Prompt a download when a file type isn't handled (pdf, etc.)

Additional context
This doesn't seem to be officially supported, but here are a few workarounds:

• can't bypass non-image file #49 (comment) Change the code to do something different (this should probably be added to this repository to provide good sensible default while still allowing people to customise even deeper). Unfortunately, this workaround is poorly documented and I'm not sure what I should do.
• can't bypass non-image file #49 (comment) Add bypasses on the CloudFront Behaviors manually, this shouldn't be necessary

Could we get a better default behavior?

[dougtoppin]

We will add an evaluation of this to our backlog

[Vadorequest]

My vision has evolved a bit since posting this, and I believe SIH should be something that would act as a "drop-in", and basically extend the capabilities of a standard CDN, not change its behavior.

Concretely, that'd mean that any kind of file that isn't supported by SIH (or Sharp) should just behave as it would when not using SIH.

This way, we could replace an existing CDN by SIH without fearing any kind of regression. That would be the best of both world, as we could use the powerful SIH feature if we want, or simply use it as a normal CDN.

The way it works right now, I had to deploy two CDN for my use-case, as modifying the default SIH behavior was too hard to do. One is used for all files, while SIH is meant to be used for images.

[github-actions]

This issue has not received a response in a while. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.

[chrisAllfasteners]

Any update?

[simonkrol]

Hi @chrisAllfasteners and @Vadorequest,

This isn't something we're currently targeting for any upcoming releases, though you could likely make this work on a basic level without too much difficulty.

Something like:

• Adding a new origin to your CloudFront distribution which points to your S3 bucket
• Setting up behaviours which match any of the extensions you want to point to SIH and ensuring they point to the existing origin
• Setting up a new default behaviour which goes to the S3 bucket

One main point to keep in mind is that this would only work if you're using Thumbor-style requests (Not the base64 encoded ones) and you can find a way to match the images you'd like to send to SIH.

Let me know how it goes,
Simon