[Cloudflare image resizing] persistent Error 9412 /HTTP 415 (apparently no origin revalidation)
Hi, please direct me to a different channel if it fits better elsewhere. I am doing worker image resizing as described here: https://developers.cloudflare.com/images/image-resizing/resize-with-workers/.
Works as designed in general, but when I bulk add images to the origin storage (public Azure Blob Storage), while some of the new images are already requested through the worker, we sometimes get images that are stuck in an error state.
These requests then always return
I did a lot of debugging, and I don't see why Cloudflare does not revalidate the origin.
- There is no custom caching in the worker
- The origin does not send cache-control headers.
- Manually purging a single upstream URL as described here https://developers.cloudflare.com/images/image-resizing/troubleshooting/#caching-and-purging does not work. (So it is some kind of cache issue)
Works as designed in general, but when I bulk add images to the origin storage (public Azure Blob Storage), while some of the new images are already requested through the worker, we sometimes get images that are stuck in an error state.
These requests then always return
HTTP 415 Unsupported Media typeCf-resized: err=9412I did a lot of debugging, and I don't see why Cloudflare does not revalidate the origin.
- There is no custom caching in the worker
- The origin does not send cache-control headers.
- Manually purging a single upstream URL as described here https://developers.cloudflare.com/images/image-resizing/troubleshooting/#caching-and-purging does not work. (So it is some kind of cache issue)
Using Image Resizing with Workers gives you powerful programmatic control over every image request.
Does the response have a Cf-Resized header? If not, then resizing has not been attempted. Possible causes:
Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news
85,042Members
Resources
Was this page helpful?
