And we wouldn't want them to be
Login to reply
Replies (2)
Long lost sibling
I think (and I don’t recall exactly) it was mainly due to caching of potential CSAM and such at that layer. We try to catch and delete them quickly but if you cache it’ll stay. Of course if you perform scanning and reviewing yourself for that cache, that is fine. And I think the deletion was an issue too, where caches usually do not respect TTL that hosts serves.