+ +
The CacheFreshenDate directive indicates that mod_proxy should +update the Date: header on documents that are +returned from the cache. CacheFreshenDate takes two arguments, an +On/Off flag and an optional +match-pattern. If the match-pattern is present, the directive +only takes effect if the request uri matches the pattern.
+ +CacheFreshenDate directives can appear in server and virtual server +configuration sections. For each request, the directives are processed +in declaration order (with virtual server directives processed before +base configuration directives). When a match, or a directive with no +pattern, is found, processing stops.
+ ++ CacheFreshenDate On "^/stories" + CacheFreshenDate Off ++ +
+ +
The ProxyResponseExpiresVector directive decouples the caching +headers of proxy responses from the caching headers received by +upstream servers. The directive indicates that mod_proxy should alter +the Expires: and Cache-Control: +max-age= headers on documents that it +returns. ProxyResponseExpiresVector takes two arguments, the number of +seconds in the future that expiry should be set to, and an +optional match-pattern. If the match-pattern is present, the +directive only takes effect if the request uri matches the +pattern.
+ +ProxyResponseExpiresVector directives can appear in server and +virtual server configuration sections. For each request, the +directives are processed in declaration order (with virtual server +directives processed before base configuration directives). When a +match, or a directive with no pattern, is found, processing stops.
+ +The expiration times indicated do not effect mod_proxy's internal +caching -- mod_proxy bases its own behavior on the headers received +from upstream servers. Downstream clients can therefore be given +longer or shorter expiration indicators than mod_proxy itself +uses. Additionally, only documents that already have an +Expires header are modified, so that non-cacheable +documents are not effected.
+ +The seconds argument should be set to 0 to +indicate immediate expiration, or -1 to explicitly +disable the header manipulation.
+ ++ # don't change expiry for images + ProxyResponseExpiresVector -1 "^/img" + # long expiration for archive + ProxyResponseExpiresVector 86400 "^/archive" + # 10-minute default expiration + ProxyResponseExpiresVector 600 ++ +
Note that CacheFreshenDate is +useful in conjunction with ProxyResponseExpiresVector
+ ++ +
The ProxyRequestHeader sets headers on upstream requests. The +first argument, one of set | unset | add | append, indicates +the action to be taken for the second argument, the +header. (The trailing colon should not be +included in the header argument.) The third argument is the +string that should be used for a set, add or append action +(for an unset, the string argument should be ommitted.)
The +optional fourth argument, match-pattern, controls the +application of the directive. If a match-pattern is present, the +request uri must match the pattern for the directive to be +applied. + +ProxyRequestHeader directives can appear in server and virtual +server configuration sections. For each request, the directives are +processed in declaration order -- base server directives processed +first. For each match found, the specified action is taken.
+ ++ ProxyRequestHeader set Language "unknown" + ProxyRequestHeader append Passed-Through this.host + <VirtualHost english.stuff.org> + ProxyRequestHeader set Language "en" + ProxyRequestHeader set Root-Request "yes" "^/$" + <VirtualHost english.stuff.org> ++ +
+ +
The ProxyResponseHeader directive sets headers on proxy +responses. The first argument, one of set | unset | add | +append, indicates the action to be taken for the second argument, +the header. (The trailing colon should not +be included in the header argument.) The third argument is the +string that should be used for a set, add or append action +(for an unset, the string argument should be ommitted.)
The +optional fourth argument, match-pattern, controls the +application of the directive. If a match-pattern is present, the +request uri must match the pattern for the directive to be +applied. + +ProxyResponseHeader directives can appear in server and virtual +server configuration sections. For each request, the directives are +processed in declaration order -- base server directives processed +first. For each match found, the specified action is taken.
+ ++ ProxyResponseHeader set X-Desert "pie" "^/deserts/pie" + ProxyResponseHeader set X-Desert "jello" "^/deserts/jello" + ProxyResponseHeader set X-Desert "jello" "^/deserts/gelatin" + ProxyResponseHeader set X-Desert "unknown" ++ +