Skip to content

Commit b04fcf0

Browse files
[http](QUERY) improve description of CACHING, clarifying what is required httpwg/http-extensions@44f43f9
1 parent c2fee94 commit b04fcf0

1 file changed

Lines changed: 29 additions & 13 deletions

File tree

http-query-method-ja.html

Lines changed: 29 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -19,8 +19,8 @@
1919
●●options
2020

2121
spec_title:The HTTP QUERY Method
22-
spec_date:2025-07-08
23-
trans_update:2025-07-10
22+
spec_date:2025-07-14
23+
trans_update:2025-07-16
2424
source_checked:250319
2525
original_url:https://httpwg.org/http-extensions/draft-ietf-httpbis-safe-method-w-body.html
2626
abbr_url:HTTPquery
@@ -746,19 +746,25 @@ <h3 title="Caching">2.5. ~cache法</h3>
746746
<p>
747747
`QUERY^m 要請~用の`~cache~key$ `HTTP-CACHING$r には、
748748
当の要請の`内容$を組入れなければナラナイ。
749-
そのためには、
750-
~cacheは,
751-
まず当の内容を次に従って正規化するベキである
752-
— 【`~cache~key$における】意味論的に有意でない相違点を除去して,
753-
それにより~cache効率を改善するために:
754749
755-
The cache key for a QUERY request (see Section 2 of [HTTP-CACHING]) MUST incorporate the request content. When doing so, caches SHOULD first normalize request content to remove semantically insignificant differences, thereby improving cache efficiency, by:
750+
The cache key for a QUERY request (see Section 2 of [HTTP-CACHING]) MUST incorporate the request content.
751+
</p>
752+
753+
<p>
754+
~cacheは、
755+
~cache効率を改善するためとして,
756+
まず【内容における】意味論的に有意でない相違点を除去してもヨイ
757+
— 一例として,次に行うことにより:
758+
759+
Caches MAY remove semantically insignificant differences first, thereby improving cache efficiency.
760+
761+
For instance, by
756762
</p>
757763
<ul>
758764
<li>
759765
`内容~符号法$(たち)を除去する。
760766
761-
Removing content encoding(s) (Section 8.4 of [HTTP]).
767+
removing content encoding(s) (Section 8.4 of [HTTP]).
762768
</li>
763769
<li>
764770
<p>
@@ -774,26 +780,36 @@ <h3 title="Caching">2.5. ~cache法</h3>
774780
を見よ)
775781
により指示される形式~規約に関する知識に基づいて正規化する。
776782
777-
Normalizing based upon knowledge of format conventions, as indicated by any media subtype suffix in the request's Content-Type field (e.g., "+json", see Section 4.2.8 of [RFC6838]).
783+
normalizing based upon knowledge of format conventions, as indicated by any media subtype suffix in the request's Content-Type field (e.g., "+json", see Section 4.2.8 of [RFC6838]).
778784
</li>
779785
<li>
780786
%~MIME型 により指示される[
781787
当の`内容$自体の意味論に関する知識
782788
]に基づいて正規化する。
783789
784-
Normalizing based upon knowledge of the semantics of the content itself, as indicated by the request's Content-Type field.
790+
normalizing based upon knowledge of the semantics of the content itself, as indicated by the request's Content-Type field.
785791
</li>
786792
</ul>
787793
</li>
788794
</ul>
789795

790796
<p>
791-
そのような正規化は
797+
そのような形式変換は
792798
もっぱら,`~cache~key$を生成する目的で遂行されることに注意
793799
— それは、
794800
当の要請~自体を変更するものではない。
795801
796-
Note that any such normalization is performed solely for the purpose of generating a cache key; it does not change the request itself.
802+
Note that any such transformation is performed solely for the purpose of generating a cache key; it does not change the request itself.
803+
</p>
804+
805+
<p>
806+
~clientは、
807+
`no-transform@~HTTPcache#cache-request-directive.no-transform$dir ~cache指令を利用して,
808+
そのような形式変換が起こらないよう望むことを指示できる
809+
(が、
810+
この指令は,助言的でしかないことに注意)。
811+
812+
Clients can indicate, using the "no-transform" cache directive (Section 5.2.1.6 of [HTTP-CACHING]), that they wish that no such transformation happens (but note that this directive is just advisory).
797813
</p>
798814

799815
</section>

0 commit comments

Comments
 (0)