| 1 |
[1] [[HTTP]] の [DFN[[CODE(HTTP)@en[[[TE:]]]]]] [[欄]]は、受け入れ可能な[[転送符号化]]を表しています。
|
| 2 |
[[クライアント]]は[[鯖]]にこの[[要求頭欄]]を提示することにより、[[鯖]]が適切な[[転送符号化]]を決定することができます。
|
| 3 |
|
| 4 |
* 歴史
|
| 5 |
|
| 6 |
[FIG[
|
| 7 |
[FIGCAPTION[
|
| 8 |
RFC 2616 (HTTP/1.1) 14.39 TE
|
| 9 |
]FIGCAPTION]
|
| 10 |
|
| 11 |
> The TE request-header field indicates what extension transfer-codings
|
| 12 |
it is willing to accept in the response and whether or not it is
|
| 13 |
willing to accept trailer fields in a chunked transfer-coding. Its
|
| 14 |
value may consist of the keyword "trailers" and/or a comma-separated
|
| 15 |
list of extension transfer-coding names with optional accept
|
| 16 |
parameters (as described in section 3.6).
|
| 17 |
|
| 18 |
TE 要求頭欄は、応答でどの拡張転送符号化を受け入れる意思があるかや、
|
| 19 |
chunked (塊) 転送符号化で trailers 欄を受け入れる意思があるか否か
|
| 20 |
を示します。値は、キーワード「trailers」と読点(comma)区切りの
|
| 21 |
拡張転送符号化の名前, 必要があれば受け入れパラメーター (3.6節で説明)
|
| 22 |
の一覧の両方または一方を取ることが出来ます。
|
| 23 |
|
| 24 |
[PRE[
|
| 25 |
TE = "TE" ":" #( t-codings )
|
| 26 |
t-codings = "trailers" | ( transfer-extension [ accept-params ] )
|
| 27 |
]PRE]
|
| 28 |
|
| 29 |
The presence of the keyword "trailers" indicates that the client is
|
| 30 |
willing to accept trailer fields in a chunked transfer-coding, as defined in
|
| 31 |
section 3.6.1. This keyword is reserved for use with transfer-coding
|
| 32 |
values even though it does not itself represent a transfer-coding.
|
| 33 |
|
| 34 |
「trailers」キーワードが現れた場合、クライアントは chunked (塊)
|
| 35 |
転送符号化において3.6.1節で定義されたように、 trailers 欄を
|
| 36 |
受け入れる意思があることを示します。このキーワードは、転送符号化を
|
| 37 |
表すものではありませんが、転送符号化値と同様に使うのに予約します。
|
| 38 |
|
| 39 |
Examples of its use are: 使用例:
|
| 40 |
|
| 41 |
- TE: deflate
|
| 42 |
- TE:
|
| 43 |
- TE: trailers, deflate;q=0.5
|
| 44 |
|
| 45 |
The TE header field only applies to the immediate connection.
|
| 46 |
Therefore, the keyword MUST be supplied within a Connection header
|
| 47 |
field (section 14.10) whenever TE is present in an HTTP/1.1 message.
|
| 48 |
|
| 49 |
TE 頭欄は、直後の接続にのみ適用されます。ですから、
|
| 50 |
TE が HTTP/1.1 メッセージ中に出現する場合は必ず、キーワードが
|
| 51 |
Connection 頭欄 (14.10節) 中にも供給され'''なければなりません'''。
|
| 52 |
|
| 53 |
A server tests whether a transfer-coding is acceptable, according to
|
| 54 |
a TE field, using these rules:
|
| 55 |
|
| 56 |
サーバーは、 TE 欄により次の規則を使って、転送符号化が使えるかどうかを
|
| 57 |
確認します。
|
| 58 |
|
| 59 |
1. The "chunked" transfer-coding is always acceptable. If the keyword
|
| 60 |
"trailers" is listed, the client indicates that it is willing to accept
|
| 61 |
trailer fields in the chunked response on behalf of itself and any downstream
|
| 62 |
clients. The implication is that, if given, the client is stating that either
|
| 63 |
all downstream clients are willing to accept trailer fields in the forwarded
|
| 64 |
response, or that it will attempt to buffer the response on behalf of
|
| 65 |
downstream recipients.
|
| 66 |
|
| 67 |
[PRE[
|
| 68 |
Note: HTTP/1.1 does not define any means to limit the size of a
|
| 69 |
chunked response such that a client can be assured of buffering
|
| 70 |
the entire response.
|
| 71 |
]PRE]
|
| 72 |
|
| 73 |
[PRE[
|
| 74 |
2. If the transfer-coding being tested is one of the transfer-
|
| 75 |
codings listed in the TE field, then it is acceptable unless it
|
| 76 |
is accompanied by a qvalue of 0. (As defined in section 3.9, a
|
| 77 |
qvalue of 0 means "not acceptable.")
|
| 78 |
]PRE]
|
| 79 |
|
| 80 |
[PRE[
|
| 81 |
3. If multiple transfer-codings are acceptable, then the
|
| 82 |
acceptable transfer-coding with the highest non-zero qvalue is
|
| 83 |
preferred. The "chunked" transfer-coding always has a qvalue
|
| 84 |
of 1.
|
| 85 |
]PRE]
|
| 86 |
|
| 87 |
If the TE field-value is empty or if no TE field is present, the only
|
| 88 |
transfer-coding is "chunked". A message with no transfer-coding is always
|
| 89 |
acceptable.
|
| 90 |
|
| 91 |
TE 欄値が空か、 TE 欄が存在しない場合、転送符号化「chunked」(塊)
|
| 92 |
だけが使えます。転送符号化の無いメッセージは常に認められます。
|
| 93 |
|
| 94 |
* ライセンス
|
| 95 |
|
| 96 |
See [[RFCのライセンス]]
|
| 97 |
]FIG]
|
| 98 |
|
| 99 |
* メモ |
Parent Directory
| 
Revision Log