When objects are marked as invalid and a client requests them, they are removed and then refreshed with new content from the origin servers.
You can choose to remove and refresh invalid objects immediately, or base the removal and refresh on the current load of the origin servers.
After the invalidation request is complete, the message that contains the comment, along with the result of the invalidation, writes to the event log: Required attribute in the invalidation preview Enter the number of objects to be listed.
If fewer objects than the number specified meet the invalidation criteria, Oracle Web Cache lists only the URLs for those objects that meet the criteria.
You can override the setting by using a pair of name/value attributes of the response-header field enables application developers to identify search key strings for a given response object.
Search keys are strings that may not appear in the URL, cookies, or HTTP request headers of objects.
The origin server adds a special invalidation header to its response.The intent of the search keys is to provide another criteria for invalidation.In addition to the URL of objects, Oracle Web Cache administrators can base invalidation on one or more search keys used in the When you send an invalidation request with an HTTP POST request, you specify the host name of Oracle Web Cache, the invalidation listening port number, and the invalidation request.The administrator need only specify which objects to invalidate and how how quickly those objects should be invalidated.Oracle Web Cache Manager enables you to send either basic invalidation request for invalidation one object, or an advanced invalidation request for multiple objects, as described in the following topics: Oracle Web Cache processes the invalidation request, and returns the Cache Cleanup Result dialog box which shows the invalidation status.