Image Optimization API should 404 when loader is not default (#18211)
We currently always accept requests to the new `/_next/image` endpoint, even when it should not be used. Instead, we should check to see if the default loader is used as a signal to enable this API. Other loaders (such as cloudinary) will not go through the Next.js API so there is no need to expose this, instead we 404. - Analogous to https://github.com/vercel/vercel/pull/5321 - Related to #18122
Showing
Please
register
or
sign in
to comment