大网数据广告活动
服务器运维问答

What's the best way to set Cache-Control headers in Apache2?

· 52CE 我爱测

Under this link you have some examples on how to set Cache-Control headers in Apache2 server. So generally, there are three different approaches to have these headers set: Using both mod_expires + mod_headers Using only mod_heade…

问题原文

原帖链接 · Mikhail Morfikov · CC BY-SA 3.0

Under this link you have some examples on how to set Cache-Control headers in Apache2 server. So generally, there are three different approaches to have these headers set:

  1. Using both mod_expires + mod_headers
  2. Using only mod_headers
  3. Using only mod_expires

Are there any significant differences between them? Which one is the preferred one and why, or maybe it doesn't matter at all? What's the best way to set Cache-Control headers in Apache2?

已采纳解答

原帖链接 · HBruijn · CC BY-SA 3.0

The main difference is that mod_expires will not replace/update Cache-Control headers if an Expires header has already been set by your web application or script and can't really be used to set anything besides the max-age Cache Control header.

The Header directive from mod_headers on the other hand can be configured to not be as considerate and will also happily merge or completely replace any existing headers to new headers you specify. That allows you to override whatever (default and not configurable) Cache-Control headers your web applications or scripts set, as well as set any other headers.

As far as I know mod_headers does not provide an interface to do the calculations that mod_expires does to calculate future dates i.e to set the Expires header to a time stamp of now + 1 month you can't use the Header directive.

So the modules are complementary.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2016-07-31)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。