[http] 各種更新

Clarify duplex semantics
httpwg/http-core#765

Mention payload -> content change
httpwg/http-core#766

Remove Canonicalization and Text Defaults
httpwg/http-core#767

No need to explain why From is bad
httpwg/http-core#762

Method semantics are inviolate
httpwg/http-core#761

Be more explicit about Content-Length errors
httpwg/http-core#760

Explicitly close the connection
httpwg/http-core#759

Move discussion of statelessness
httpwg/http-core#758

rephrase connection closure incomplete (editorial)
httpwg/http-core#755

Broaden cache poisoning
httpwg/http-core#757

Define 'cache key'
httpwg/http-core#756

Fixes for TLS connection closure
httpwg/http-core#734

remove "charset" ABNF production and explain where charsets occur
editorial semantics
httpwg/http-core#752

http-cache-ja.html

@@ -12,8 +12,8 @@
 
 ●●options
 spec_title:HTTP Caching
-spec_date:2021-01-16
-trans_update:2021-01-23
+spec_date:2021-02-11
+trans_update:2021-02-12
 source_checked:201210
 page_state_key:HTTP
 original_url:https://httpwg.org/http-core/draft-ietf-httpbis-cache-latest.html
@@ -774,7 +774,7 @@ <h2 title="Overview of Cache Operation">2. ~cache運用の概観</h2>
 
 <p>
 `~cache~key@
-は、最小でも，格納-済み応答を検索取得するために利用された［
+は，格納-済み応答を選定するために~cacheが利用する情報であり、最小でも，格納-済み応答を検索取得するために利用される［
 `要請~method$,
 `~target~URI$
 ］からなる
@@ -785,7 +785,7 @@ <h2 title="Overview of Cache Operation">2. ~cache運用の概観</h2>
 `GET$m に対する応答のみを~cacheして，他の~methodは回送している
 ］ので，~cache~keyとして~URIしか利用していない。
 ◎
-The cache key is comprised of, at a minimum, the request method and target URI used to retrieve the stored response; the method determines under which circumstances that response can be used to satisfy a subsequent request. However, many HTTP caches in common use today only cache GET responses, and therefore only use the URI as the cache key, forwarding other methods.
+The cache key is the information a cache uses to select a response and is comprised of, at a minimum, the request method and target URI used to retrieve the stored response; the method determines under which circumstances that response can be used to satisfy a subsequent request. However, many HTTP caches in common use today only cache GET responses, and therefore only use the URI as the cache key, forwarding other methods.
 </p>
 
 <p>
@@ -3788,15 +3788,15 @@ <h2 title="Security Considerations">7. ~securityの考慮点</h2>
 <h3 title="Cache Poisoning">7.1. ~cache汚染</h3>
 
 <p>
-様々な攻撃が，`共用~cache$内に格納されることにより増幅され得る。
-そのような “~cache汚染” 攻撃は、［
-多数の`~client$に向けて悪意的な`内容$を配布する
-］ような~cacheを利用する。
-それは、攻撃者が［
+様々な攻撃が，~cache内に格納されることにより増幅され得る。
+そのような “~cache汚染” 攻撃は、攻撃者が［
 実装の欠陥, 特権拡大, その他の技法
-］を利用して，そのような応答を~cacheの中へ挿入できるときには、とりわけ効果的になる。
+］を利用して，~cacheの中へ応答を挿入するときに起こる。
+これは、［
+多数の`~client$に悪意的な`内容$を配布するために，`共用~cache$が利用される
+］とき，とりわけ効果的になる。
 ◎
-Various attacks might be amplified by being stored in a shared cache. Such "cache poisoning" attacks use the cache to distribute malicious content to many clients, and are especially effective when an attacker can use implementation flaws, elevated privileges, or other techniques to insert such a response into a cache.
+Various attacks might be amplified by being stored in a cache. Such "cache poisoning" attacks happen when an attacker uses implementation flaws, elevated privileges, or other techniques to insert a response into a cache. This is especially effective when shared caches are used to distribute malicious content to many clients.
 </p>
 
 <p>

http-common.js

@@ -425,7 +425,6 @@ p.date3:~HTTPinfra#p.date3
 	//Semantics
 p.byte-content-range:~HTTPsem#p.byte-content-range
 p.byte-range-resp:~HTTPsem#p.byte-range-resp
-p.charset:~HTTPsem#p.charset
 p.complete-length:~HTTPsem#p.complete-length
 p.connection-option:~HTTPsem#p.connection-option
 p.content-coding:~HTTPsem#p.content-coding
@@ -1178,8 +1177,6 @@ escaping::::エスケープ処理
 単数:singleton:::~
 桁:digit::~
 	構文~上:syntactical
-正準-:canonical::~
-	正準-化:canonicalization
 移行:transition::~
 稀:rare:~
 番号:number:~