Custom Emojis loaded from S3/R2 bypass CDN routing

[Falco]

Discourse uses a two CDN setup, one for assets and one proxying the app.

Standard emoji uses one CDN, custom emoji uses the other CDN, but both are protected by a CDN on a properly configured website with a working two CDN setup.

I went over that in the first related topic here

Custom emoji don't use CDN for S3 stored assets in a few pages

Custom emoji for testing Non custom emoji So standard emoji use one CDN while custom use another, but both are covered by CDN if you do a proper configuration following Using Object Storage for Uploads (S3 Clones) to the letter. Not a bug, this is expected behavior because standard emoji is stored inside the app codebase and custom is just a normal site upload.

Does your site have both CDNs setup and working?