You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add a new pet to pets.json along with a new image to src/images
Run netlify dev
The new image 404s:
I thought perhaps the netlify.toml needed to also account for the :height parameter in the requests, eg
[[redirects]]
from = "/cloudinaried/:height/*"to = "/images/:splat"status = 404
But that didn't seem to work either.
Accessing the image directly when netlify dev is running at http://localhost:8888/images/the-new-doggo.jpg works as expected.
Has the syntax changed since this was originally written?
The idea of having 404s at Cloudinary fall back to the local, untransformed image is very appealing for local development and working with deploy previews, so I'm curious if I'm missing something here.
The text was updated successfully, but these errors were encountered:
This is extremely NOT urgent please do not go out of your way to answer this.
I was playing around with this after I found it via CSS-Tricks and your tweet https://twitter.com/philhawksworth/status/1328340868726726656 about using Cloudinary and Netlify redirects, but with a 404 handler to re-serve local images as mentioned here https://twitter.com/philhawksworth/status/1328350104340848641.
But I'm not sure if it's working these days?
Reproduce
npm install
netlify dev
The new image 404s:
I thought perhaps the netlify.toml needed to also account for the :height parameter in the requests, eg
But that didn't seem to work either.
Accessing the image directly when
netlify dev
is running athttp://localhost:8888/images/the-new-doggo.jpg
works as expected.Has the syntax changed since this was originally written?
The idea of having 404s at Cloudinary fall back to the local, untransformed image is very appealing for local development and working with deploy previews, so I'm curious if I'm missing something here.
The text was updated successfully, but these errors were encountered: