On Tue, 25 Jul 2000, Gregory A. Ivanov wrote:
> ������ - ������ ��� ���������� IMS ���� Expire ��� �� �������� ? �
> ��� ���� ������� ����� ��� �� ����������? ������ ���������� ��� ������
> � image/gif � image/jpg, � text/html ��� � �������.
>
> ��� ��� ������ ������:
>
> �� ��������:
> HTTP/1.1 200 OK
> Date: Tue, 25 Jul 2000 12:00:20 GMT
> Server: Apache/1.3.12 (Unix) mod_perl/1.24 rus/PL29.7
> Cache-Control: max-age=3600
^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Expires: Tue, 25 Jul 2000 13:00:20 GMT
> Last-Modified: Fri, 14 Jul 2000 14:11:24 GMT
> ETag: "340c4-23-396f1f8c"
> Accept-Ranges: bytes
> Content-Length: 35
> Content-Type: image/gif
rfc2068:
13.2.4 Expiration Calculations
In order to decide whether a response is fresh or stale, we need to
compare its freshness lifetime to its age. The age is calculated as
described in section 13.2.3; this section describes how to calculate
the freshness lifetime, and to determine if a response has expired.
In the discussion below, the values can be represented in any form
appropriate for arithmetic operations.
We use the term "expires_value" to denote the value of the Expires
header. We use the term "max_age_value" to denote an appropriate
value of the number of seconds carried by the max-age directive of
the Cache-Control header in a response (see section 14.10.
> The max-age directive takes priority over Expires, so if max-age is
> present in a response, the calculation is simply:
>
> freshness_lifetime = max_age_value
Otherwise, if Expires is present in the response, the calculation is:
freshness_lifetime = expires_value - date_value
��� ��� ���� �������� �������� ���������� ��� � ���, �� �ӣ ��������
���������. ���� ��� ���, �� ����� �� ������ ������� ������
Cache-Control: max-age
Regards!
Igor Khasilev |
PACO Links, [EMAIL PROTECTED] |
=====================================================================
If you would like to unsubscribe from this list send message to
[EMAIL PROTECTED] with "unsubscribe oops" in message body.
Archive is accessible on http://www.paco.net/oops/