Lines Matching refs:age
212 /* do a HTTP/1.1 age calculation */
223 /* Perform an HTTP/1.1 age calculation. (RFC2616 13.2.3) */
255 * request dies, the lock will be trashed when its max-age is reached,
518 apr_int64_t age, maxage_req, maxage_cresp, maxage, smaxage, maxstale;
551 * maximum age an object can be before it is considered stale. This
555 * - RFC2616 14.9.4 Cache-Control: max-age this header can appear in both
600 /* calculate age of object */
601 age = ap_cache_current_age(info, age_c, r->request_time);
606 /* extract max-age from request */
613 * extract max-age from response, if both s-maxage and max-age, s-maxage
644 * to accept a stale response of any age (RFC2616 14.9.3). We will
672 if (((maxage != -1) && (age < (maxage + maxstale - minfresh))) ||
675 (age < (apr_time_sec(info->expire - info->date) + maxstale - minfresh)))) {
680 /* set age header on response */
682 apr_psprintf(r->pool, "%lu", (unsigned long)age));
685 if (!(((maxage != -1) && age < maxage) ||
687 (apr_time_sec(info->expire - info->date)) > age))) {
697 * If none of Expires, Cache-Control: max-age, or Cache-Control:
698 * s-maxage appears in the response, and the response header age
702 h->resp_hdrs, "Expires") == NULL) && (age > 86400)) {
744 * A lock that exceeds a maximum age will be deleted, and another
1045 if (!strcmp(token, "max-age=0")) {
1053 else if (!strncasecmp(token, "max-age", 7)) {