h3c 802.1x client Principle analysis of using client cache to optimize website Page 1/2

Many people first want to optimize the program from the server caching aspect. Many different server caching methods have their own characteristics. For example, in some projects I have participated in, Com+/Enterprise Libiary Caching was used based on the cache hit rate. Server-side caching and HTTP Compression technology in Windows services, static files, etc., but client-side caching is often ignored by people. Even if the server’s cache makes your page access very fast, it still needs to rely on browser downloads. And output, and when you add client-side caching, it will bring you a lot of benefits. Because she can cache the most frequently accessed pages in the site, fully improving the throughput of the Web server (usually in terms of requests per second data computing) to improve application performance and scalability.
An online shopping survey shows that most people are willing to queue in stores, but are not willing to wait when shopping online. Websense research company claims that as many as 70% of Internet users are unwilling to read a page for more than 10 seconds. More than 70% of people will cancel their current order because the speed is too slow.
Basic knowledge
1) What is "Last-Modified"?
When the browser requests a URL for the first time, the return status from the server will be 200, the content is the resource you requested, and there is a Last-Modified attribute. Mark the time when this file was last modified on the server side. The format is similar to this:
Last-Modified: Fri, 12 May 2006 18:53:33 GMT
When the client requests this URL for the second time, according to the provisions of the HTTP protocol, The browser will send the If-Modified-Since header to the server, asking whether the file has been modified after this time:
If-Modified-Since: Fri, 12 May 2006 18:53:33 GMT
If the server-side resources have not changed, Then the HTTP 304 (Not Changed.) status code is automatically returned, and the content is empty, thus saving the amount of data to be transmitted. When the server-side code changes or the server is restarted, the resource is reissued and the return is similar to the first request. This ensures that resources are not sent to the client repeatedly, and also ensures that when the server changes, the client can get the latest resources.
2) What is "Etag"?
HTTP protocol specification defines ETag as "the entity value of the requested variable" (see - Chapter 14.19). Another way to put it is that an ETag is a token that can be associated with a Web resource. A typical web resource would be a web page, but it could also be a JSON or XML document. The server is solely responsible for determining what the token is and its meaning, and transmits it to the client in the HTTP response header. The following is the format returned by the server:
ETag: "50b1c1d4f775c61:df3"
The client's query update format is as follows:
If-None-Match: W/"50b1c1d4f775c61:df3"
If the ETag has not changed, status 304 will be returned and then not returned, which is the same as Last-Modified. I tested Etag mainly to be useful during breakpoint downloads.
How do Last-Modified and Etags help improve performance?
Smart developers will use Last-Modified and ETags request http headers together, which can take advantage of the cache of the client (such as the browser). Because the server generates the Last-Modified/Etag tag first, the server can use it later to determine whether the page has been modified. Essentially, the client is asking the server to validate its (client-side) cache by passing this token back to the server.
The process is as follows:
1. The client requests a page (A).
2. The server returns page A and adds a Last-Modified/ETag to A.
3. The client displays the page and caches the page together with Last-Modified/ETag.
4. The client requests page A again and passes the Last-Modified/ETag returned by the server in the last request to the server.
5. The server checks the Last-Modified or ETag and determines that the page has not been modified since the last client request, and directly returns response 304 and an empty response body.
The following example describes how to use server-side code to operate client-side cache:

Current page 1/2 12Next page

The above introduces the principle analysis of h3c 802.1x client using client cache to optimize the website, page 1/2, including the content of h3c 802.1x client. I hope it will be helpful to friends who are interested in PHP tutorials.