200 206
Pragma: If-Modified-Since: 304
304_representation_metadata に含まれています。
If the client has performed a conditional GET request and access is allowed, but the document has not been modified
, the server{1945}since the date and time specified in the If-Modified-Since field{1945}must{2068}SHOULD respond with this status code.{1945}and not send an Entity-Body to the client{2068,2616}The 304 response MUST NOT contain a message-body, {2616} and thus is always terminated by the first empty line after the header fields.{1945}Header fields contained in the response should only include information which is relevant to cache managers or which may have changed independently of the entity's Last-Modified date. Examples of relevant header fields include: Date, Server, and Expires. A cache should update its cached entity to reflect any new field values given in the 304 response.
クライアントが条件付き してはならず、クライアントに するべきです。304 応答は 応答中に含まれる頭欄はキャッシュ管理器に関係する情報又は実体の 304 応答で与えられた新しい欄値を反映するように更新するべきです。
{2068,2616} The response MUST include the following header fields:
- Date, unless its omission is required by section 14.18.1
応答は次の頭欄を含まなければなりません:
Date 省略が義務付けられている場合を除く{2616} If a clockless origin server obeys these rules, and proxies and clients add their own Date to any response received without one (as already specified by [RFC 2068], section 14.19), caches will operate correctly.
時計のない起源サーバーはこれらの規則に従い、
串及びクライアントが自身の Date を Date
なしで受信した応答に付け加えれば、
キャッシュは正しく処理されます。
- ETag and/or Content-Location, if the header would have been sent in a 200 response to the same request
- Expires, Cache-Control, and/or Vary, if the field-value might differ from that sent in any previous response for the same variant
ETag Content-Location 200 Expires Cache-Control Vary If the conditional GET used a strong cache validator (see section 13.3.3), the response SHOULD NOT include other entity-headers. Otherwise (i.e., the conditional GET used a weak validator), the response MUST NOT include other entity-headers; this prevents inconsistencies between cached entity-bodies and updated headers.
条件付き GET がGET が弱い検証を使っているなら、)
応答は他の実体頭欄を含んではなりません。
これによってキャッシュされている実体本体と更新された頭の不一致を防ぐことができます。
If a 304 response indicates an entity not currently cached, then the cache MUST disregard the response and repeat the request without the conditional.
304 応答が実体は現在キャッシュされていないことを示すなら、
その時はキャッシュは応答を捨てて条件付きでない要求を繰り返さなければなりません。
If a cache uses a received 304 response to update a cache entry, the cache MUST update the entry to reflect any new field values given in the response.
キャッシュが受信した 304 応答を使ってキャッシュ項目を更新するなら、
キャッシュは応答中に与えられた新しい欄値を反映して実体を更新しなければなりません。
{2068} The 304 response MUST NOT include a message-body, and thus is always terminated by the first empty line after the header fields.
304 応答は