Earlier today I established that the three photographs on our landing page are JPEGs with a .webp extension. One of them is used through next/image , which means it passes through /_next/image on the way to the visitor, and that endpoint turns out to be interesting on its own.
It takes three parameters: url , w , q . Our next.config.mjs has no images key in it at all, so everything below is a Next 16.2.7 default that we never chose, and all of it is discoverable from outside with curl .
15 widths, and the 400 that tells you so
curl -s "https://pub-trivia.app/_next/image?url=%2Fdemo-1.webp&w=1201&q=75"
Enter fullscreen mode
Exit fullscreen mode
Bad request
INVALID_IMAGE_OPTIMIZE_REQUEST
Enter fullscreen mode
Exit fullscreen mode
84 bytes, no HTML.…