Activate F5 product registration key
Verify the proper operation of your BIG-IP system
Get up to speed with free self-paced courses
Join the community of 250,000+ technical peers
Advance your career with F5 Certification
Product Manuals and Release notes
Responses from origin web servers include entity tags (ETags), which are arbitrary strings attached to a document that specify some characteristic of the document, such as a version, serial number, or checksum of content. A changed document includes a different ETag, enabling a client's GET request to use an If-None-Match conditional header to acquire a new copy of the document. Because not all web applications generate ETags consistently, the BIG-IP creates its own ETag for each cached document that is based on a signature, or checksum, of the document's content. The BIG-IP stores content signatures in the Metadata cache for other optimizations, including Intelligent Browser Referencing.
BIG-IP applications provide options to always or never send metadata. Additionally, you can specify a maximum size for the Metadata cache, in megabytes. All BIG-IP applications share the same Metadata cache.
BIG-IP policies cache ETag headers, which include the following: