ids/2/191.txt



* 仕様書から


** RFC 2616 (HTTP/1.1) 14.39 TE

> The TE request-header field indicates what extension transfer-codings
it is willing to accept in the response and whether or not it is
willing to accept trailer fields in a chunked transfer-coding. Its
value may consist of the keyword "trailers" and/or a comma-separated
list of extension transfer-coding names with optional accept
parameters (as described in section 3.6).

TE 要求頭領域は、応答でどの拡張転送符号化を受け入れる意思があるかや、
chunked (塊) 転送符号化で尻尾領域を受け入れる意思があるか否か
を示します。値は、キーワード「trailers」(尻尾)と読点(comma)区切りの
拡張転送符号化の名前, 必要があれば受け入れパラメーター (3.6節で説明) 
の一覧の両方または一方を取ることが出来ます。

[PRE[
       TE        = "TE" ":" #( t-codings )
       t-codings = "trailers" | ( transfer-extension [ accept-params ] )
]PRE]

The presence of the keyword "trailers" indicates that the client is
willing to accept trailer fields in a chunked transfer-coding, as defined in 
section 3.6.1. This keyword is reserved for use with transfer-coding 
values even though it does not itself represent a transfer-coding.

「trailers」(尻尾)キーワードが現れた場合、クライアントは chunked (塊)
転送符号化において3.6.1節で定義されたように、尻尾領域を
受け入れる意思があることを示します。このキーワードは、転送符号化を
表すものではありませんが、転送符号化値と同様に使うのに予約します。

Examples of its use are: 使用例:

- TE: deflate
- TE:
- TE: trailers, deflate;q=0.5

The TE header field only applies to the immediate connection.
Therefore, the keyword MUST be supplied within a Connection header
field (section 14.10) whenever TE is present in an HTTP/1.1 message.

TE 頭領域は、直後の接続にのみ適用されます。ですから、
TE が HTTP/1.1 メッセージ中に出現する場合は必ず、キーワードが 
Connection 頭領域 (14.10節) 中にも供給され'''なければなりません'''。

A server tests whether a transfer-coding is acceptable, according to
a TE field, using these rules:

サーバーは、 TE 領域により次の規則を使って、転送符号化が使えるかどうかを
確認します。

1. The "chunked" transfer-coding is always acceptable. If the keyword 
"trailers" is listed, the client indicates that it is willing to accept 
trailer fields in the chunked response on behalf of itself and any downstream 
clients. The implication is that, if given, the client is stating that either 
all downstream clients are willing to accept trailer fields in the forwarded 
response, or that it will attempt to buffer the response on behalf of 
downstream recipients.

[PRE[
         Note: HTTP/1.1 does not define any means to limit the size of a
         chunked response such that a client can be assured of buffering
         the entire response.
]PRE]

[PRE[
      2. If the transfer-coding being tested is one of the transfer-
         codings listed in the TE field, then it is acceptable unless it
         is accompanied by a qvalue of 0. (As defined in section 3.9, a
         qvalue of 0 means "not acceptable.")
]PRE]

[PRE[
      3. If multiple transfer-codings are acceptable, then the
         acceptable transfer-coding with the highest non-zero qvalue is
         preferred.  The "chunked" transfer-coding always has a qvalue
         of 1.
]PRE]

If the TE field-value is empty or if no TE field is present, the only 
transfer-coding  is "chunked". A message with no transfer-coding is always 
acceptable.

TE 領域値が空か、 TE 領域が存在しない場合、転送符号化「chunked」(塊)
だけが使えます。転送符号化の無いメッセージは常に認められます。


** ライセンス

See [[RFCのライセンス]]


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