Large media: source image

Support
3

Ahhhh interesting…

I hadn’t thought about creating my own URLs which then use the redirects engine to proxy to the URLs as they correspond to my image paths in git

My one concern is that, for my use case, this could apply to possibly >1,000 image paths—does that have a performance drawback? I’m going to guess no, because ultimately (as in your example) you’re only writing one redirect rule, it just might apply to an innumerable number of paths.

[[redirects]]
  from = "/img/:width/:image"
  to = "https://my-app.netlify.app/images/:image?nf_resize=fit&w=:width"
  status = 200

Ultimately the original source image would still be available online, but if nobody has access to my GitHub repo, they won’t know what that original path is unless they just start guessing at paths off the root until they find something.

I think that might actually be a viable option! Thanks for thinking out loud.

1 Like