.net Review the past and learn the new [14]: Asp.Net Core WebAPI cache

.net Review the past and learn the new [14]: Asp.Net Core WebAPI cache 1. Cache Caching refers to the act of storing data in an intermediary tier that makes subsequent data retrieval faster. Conceptually, caching is a performance optimization strategy and design consideration. Caching can significantly improve application performance by improving the readiness of data that changes infrequently (or is expensive to retrieve). 二、RFC9111 In the latest cache control specification document RFC9111, the specifications for browser cache and server cache control are described in detail, including the most important response message header Cache-Control. The setting of this header will affect our cache, both on the browser side and on the server side. RFC911: https://www.rfc-editor.org/rfc/rfc9111#name-cache-control 3. Web-side cache In Cache-Control, if you set max-age=10, it means telling the browser to cache for 10s. Why does the browser recognize this? The front and back ends we mentioned above must be implemented according to the RFC standard specification, which is a unified socket for the hardware, otherwise the other generated ones will not be used. Then in Asp.net Core, you only need to add ResponseCacheAttribute to the interface and set the max-age time. First build an Asp.Net Core WebAPI project and write a…