ETag vs Header Expires

by

They are slightly different – the ETag does not have any information that the client can use to determine whether or not to make a request for that file again in the future. If ETag is all it has, it will always have to make a request. However, when the server reads the ETag from the client request, the server can then determine whether to send the file (HTTP 200) or tell the client to just use their local copy (HTTP 304). An ETag is basically just a checksum for a file that semantically changes when the content of the file changes.

The Expires header is used by the client (and proxies/caches) to determine whether or not it even needs to make a request to the server at all. The closer you are to the Expires date, the more likely it is the client (or proxy) will make an HTTP request for that file from the server.

So really what you want to do is use BOTH headers – set the Expires header to a reasonable value based on how often the content changes. Then configure ETags to be sent so that when clients DO send a request to the server, it can more easily determine whether or not to send the file back.

One last note about ETag – if you are using a load-balanced server setup with multiple machines running Apache you will probably want to turn off ETag generation. This is because inodes are used as part of the ETag hash algorithm which will be different between the servers. You can configure Apache to not use inodes as part of the calculation but then you’d want to make sure the timestamps on the files are exactly the same, to ensure the same ETag gets generated for all servers.

More Related Contents:

  1. What requests do browsers’ “F5” and “Ctrl + F5” refreshes generate?
  2. What’s the difference between Cache-Control: max-age=0 and no-cache?
  3. What is the difference between HTTP status code 200 (cache) vs status code 304?
  4. Ideal HTTP cache control headers for different types of resources
  5. Why both no-cache and no-store should be used in HTTP response?
  6. What is the function of the “Vary: Accept” HTTP header?
  7. What is Cache-Control: private?
  8. Avoid caching of the http responses
  9. HTTP Headers: Controlling Cache and History Mechanism
  10. What is the difference between POST and PUT in HTTP?
  11. How long do browsers cache HTTP 301s?
  12. Correct way to pass multiple values for same parameter name in GET request
  13. HTTP 1.0 vs 1.1
  14. HTTP GET in VBS
  15. URL: Username with @
  16. HTTP Range header
  17. Where can I find the default timeout settings for all browsers?
  18. How to send password securely over HTTP?
  19. Content-Length header with HEAD requests?
  20. Why can’t browser send gzip request?
  21. What is the main difference between PATCH and PUT request?
  22. How to pass basic auth credentials in API call for a Flutter mobile application?
  23. Process Management for the Go Webserver
  24. How to send line break with curl?
  25. Share a cookie between two websites
  26. What is HTTP “Host” header?
  27. nginx upload client_max_body_size issue
  28. “Cannot GET /” with Connect on Node.js
  29. Can a http server detect that a client has cancelled their request?
  30. Should cookie values be URL encoded?

Leave a Comment