blocks|key|701155|text|Cache-Control是在HTTP1.1中引入的，它提供了比Expires更多的选项。它们可以用来完成相同的事情，但是Expires的数据值是一个Cache-Control日期，而HTTP+age允许您指定一个相对的时间量，因此您可以指定“页面被请求后的X小时”。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|701156|HTML+Cache+control是一个非常类似的问题，并且有一个很好的缓存教程链接，可以回答你的大多数问题(例如，http://www.mnot.net/cache_docs/#EXPIRES)。综上所述，当您需要更多地控制如何进行缓存时，建议将Expires用于图像和Cache-Control等静态资源。|701157|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/3099526/html-cache-control|1|http://www.mnot.net/cache_docs/#EXPIRES^0|0|D|W|7|1P|7|23|D|0|3H|7|3T|D|0|I|0|1N|13|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]|$9|U|A|V|B|C]|$9|W|A|X|B|C]|$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|10|8|@$9|11|A|12|B|C]|$9|13|A|14|B|C]]|D|@$9|15|A|16|1|17]|$9|18|A|19|1|1A]]|E|$]]|$1|H|3|-4|5|6|7|1B|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]|P|$5|K|L|M|E|$N|Q]]]]

<code>Cache-Control</code> was introduced in HTTP/1.1 and offers more options than <code>Expires</code>. They can be used to accomplish the same thing but the data value for <code>Expires</code> is an HTTP date whereas <code>Cache-Control</code> max-age lets you specify a relative amount of time so you could specify "X hours after the page was requested". 

<a href="https://stackoverflow.com/questions/3099526/html-cache-control">HTML Cache control</a> is a very similar question and has a good link to a caching tutorial that should answer most of your questions (e.g., <a href="http://www.mnot.net/cache_docs/#EXPIRES" rel="noreferrer">http://www.mnot.net/cache_docs/#EXPIRES</a>). To sum up though, <code>Expires</code> is recommended for static resources like images and <code>Cache-Control</code> when you need more control over how caching is done.

blocks|key|917383|text|如果您使用的是CDN+(Cloud+Delivery+Network，云交付网络)，我建议您使用Cache-Control，并设置最大使用时间(以秒为单位)。例如Cache-Control:+max-age=604800。这可以防止对您的源站的请求峰值:使用"Expires+Wed，30+Oct+20xx+04:37:07+GMT“所有浏览器将同时请求您。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|917384|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If you are using a CDN (Cloud Delivery Network) I recommend to use Cache-Control with a max-age time in seconds. For example Cache-Control: max-age=604800. 
This prevents request-peaks to your origin-server: With "Expires Wed, 30 Oct 20xx 04:37:07 GMT" all browsers will request you at the same time.

blocks|key|701281|text|Cache-Control是在HTTP/1.1中定义的，它告诉从服务器到客户端的所有缓存机制是否可以缓存此对象。它以秒为单位：Cache-Control:+max-age=3600。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|701282|Expires标头字段提供日期/时间，在此日期/时间之后，响应将被视为过期。Expires值是一个HTTP-date时间戳：Expires:+Tue,+18+Jul+2017+16:07:23+GMT。|701283|如果响应在max-age指令中包含Cache-Control字段，则收件人必须忽略Expires字段。|701284|entityMap^0|1R|R|0|0|7|1Q|12|0|5|7|H|D|15|7|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|T|8|@$9|U|A|V|B|C]|$9|W|A|X|B|C]|$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|J|3|-4|5|6|7|10|8|@]|D|@]|E|$]]]|K|$]]

Cache-Control was defined in HTTP/1.1, tells all caching mechanisms from server to client whether they may cache this object. It is measured in seconds: <code>Cache-Control: max-age=3600</code>. 

The <code>Expires</code> header field gives the date/time after which the response is considered stale. The Expires value is an HTTP-date timestamp: <code>Expires: Tue, 18 Jul 2017 16:07:23 GMT</code>.

If a response includes a <code>Cache-Control</code> field with the <code>max-age</code> directive, a recipient MUST ignore the <code>Expires</code> field.

blocks|key|701312|text|如果你仍然感兴趣，我直接把这个推荐留给谷歌的孩子们。与缓存控制相比，它们更喜欢在过期之前到期的https://developers.google.com/speed/docs/insights/LeverageBrowserCaching|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|701313|entityMap|0|LINK|mutability|MUTABLE|url|https://developers.google.com/speed/docs/insights/LeverageBrowserCaching^0|1B|20|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

If you are still interested, I leave this recommendation directly from google's boys.
<a href="https://developers.google.com/speed/docs/insights/LeverageBrowserCaching" rel="nofollow noreferrer">https://developers.google.com/speed/docs/insights/LeverageBrowserCaching</a> 
They prefer Expires before than Cache-Control

blocks|key|701377|text|除了CC的私有/公共选项之外，我看不出有什么不同。当使用像“访问加一年/月/周/天”这样的过期时，它的工作方式与CC完全相同。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|701378|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Except for the private/public options of CC, I can't see any difference. When using Expires like "access plus 1 year/month/week/day", it works in exactly the same way as CC does.

What’s the difference between <code>Expires</code> and <code>Cache-Control</code> headers?

what’s the difference between Expires and Cache-Control headers?

服务器

Expires和Cache-Control报头有什么不同？

问Expires和Cache-Control头有什么区别？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Expires和Cache-Control头有什么区别？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Expires和Cache-Control头有什么区别？
EN