![]() ![]() ![]() It's also relatively unusual that a 400 or 404 error is later fixed and becomes a successful response, so we need to cache those as long as possible for performance reasons. ![]() Regarding the CDN cache, the issue with purging the cache 'early' is that for failed requests we don't have any identifier that can be referenced and used as the invalidation criteria (i.e there's no entry in your account's database for images that don't exist for us to look up to know which URLs should be invalidated). When fetching remote images is allowed, you can use that field to limit the URLs that can be fetched (note that you also still use the API or a signature to override that list of domains if needed, the limitation is for unauthenticated requests) The text box further down the same page marked "Allowed fetch domains:" is a separate/parallel configuration option. Apologies if you mentioned that that specifically and I missed it, but to clarify: checked = restricted, unchecked = publicly-accessible. The checkbox being filled means that the type is 'restricted', so assets of that type can only be accessed with a signature or created programmatically via the API. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |