![]() ![]() Intel recognizes that debug capabilities contained within the hardware can be an attack surface used by adversaries to gain access to secure assets and private user data. The term “debug” spans a wide variety of use models from internal hardware debug through debug of performance issues of software running on the silicon. Intel is not unique in this regard other silicon engineering companies include these or similar types of capabilities in order to bring products to market. Unlike software debug features which can be excluded in production software, the nature of silicon development precludes hardware features from being removed in the final production silicon. As a result, Intel silicon contains several different technology capabilities used to debug its silicon. It is a criterion for whether a response is fresh or stale.Debug is a critical capability of any system in order to get the system from manufacturing to production to deployment. Cache storage isn't required to remove stale responses immediately because revalidation could change the response from being stale to being fresh again. This usually means the response can't be reused as-is. Indicates that the response is a stale response. This usually means the response can be reused for subsequent requests, depending on request directives. Usually, the revalidation is done through a conditional request. Revalidate responseĪsk the origin server whether or not the stored response is still fresh. Reuse cached responses for subsequent requests. (Usually, "cache" means storing a response.) Reuse response However, the cached response is not always reused as-is. Store a response in caches when the response is cacheable. It can store and reuse personalized content for a single user. It is also called local cache or browser cache. Private cacheĬache that exists in the client. It stores a single response and reuses it with multiple users - so developers should avoid storing personalized contents to be cached in the shared cache. Shared cacheĬache that exists between the origin server and clients (e.g. It can be either a shared cache or a private cache. Implementation that holds requests and responses for reusing in subsequent requests. This section defines the terms used in this document, some of which are from the specification.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |