js定义map:急!急!急!计算机专业英语翻译

来源:百度文库 编辑:高考问答 时间:2024/05/08 19:44:11
The extension-header mechanism allows additional entity-header fields to be defined without changing the protocol,
but these fields cannot be assumed to be recognizable by the recipient. Unrecognized header fields SHOULD be
ignored by the recipient and MUST be forwarded by transparent proxies.
7.2 Entity Body
The entity-body (if any) sent with an HTTP request or response is in a format and encoding defined by the entity-
header fields.
entity-body
= *OCTET
An entity-body is only present in a message when a message-body is present, as described in section 4.3. The entity-
body is obtained from the message-body by decoding any Transfer-Encoding that might have been applied to
ensure safe and proper transfer of the message.
7.2.1 Type
When an entity-body is included with a message, the data type of that body is determined via the header fields
Content-Type and Content-Encoding. These define a two-layer, ordered encoding model:
entity-body := Content-Encoding( Content-Type( data ) )
Content-Type specifies the media type of the underlying data. Content-Encoding may be used to indicate
any additional content codings applied to the data, usually for the purpose of data compression, that are a property of
the requested resource. There is no default encoding.
Any HTTP/1.1 message containing an entity-body SHOULD include a Content-Type header field defining the
media type of that body. If and only if the media type is not given by a Content-Type field, the recipient MAY
attempt to guess the media type via inspection of its content and/or the name extension(s) of the URI used to identify
the resource. If the media type remains unknown, the recipient SHOULD treat it as type “application/octet-
stream”.
7.2.2 Entity Length
The entity-length of a message is the length of the message-body before any transfer-codings have been applied.
Section 4.4 defines how the transfer-length of a message-body is determined.
8 Connections
8.1 Persistent Connections
8.1.1 Purpose
Prior to persistent connections, a separate TCP connection was established to fetch each URL, increasing the load on
后面还有!!!

延长- 首领的机制允许另外的要不需要变更记录就被定义的实体- 首领的领域,
但是这些领域不能够被假定在~手边接受者是可认识的。 未被认识的首领领域应该是
藉着接受者忽略而且一定被透明代理转寄。
7.2 实体身体
实体- 与一个 HTTP 请求或回应一起送的身体 ( 如果任何的) 以一的格式和被实体定义的入码-
首领回答。
实体- 身体
=* 八个位元
一个实体- 身体是一个信息的唯一礼物当一个信息-身体是礼物,如第 4.3 节所描述。 实体-
身体从信息被获得- 身体藉由解码任何的入码移动的那可能被应用到
确定信息的安全和适当移动。
7.2.1 类型
当一个实体- 身体和一个信息包含在一起, 那一个身体的数据类型经由首领被决定领域
使-满足类型和内容-入码。 这些定义一二-层,命令了入码模型:
实体- 身体 :=入码内容的 (内容-类型 ( 数据 ))
内容-类型叙述在下面的数据媒体类型。 内容- 入码可能用来指出
任何的另外内容 codings 适用于数据, 通常为了数据压缩,那是财产
被请求的资源。 没有假设值入码。
任何的 HTTP/1.1个信息包含一个实体- 身体应该包括一个内容- 类型的首领领域定义那
那一个身体的媒体类型。 如果而且只有当如果媒体类型不是被一个内容- 类型的领域给的, 接受者五月
经由它的内容及[或] 用来识别的 URI 的名字延长 (s) 的检验尝试猜测媒体类型
资源。 如果媒体类型一直没没无闻, 接受者应该视它为类型 "申请/八个位元-
水流".
7.2.2 实体长度
信息的实体长是信息的长度-在任何的移动前的身体-codings 已经被应用。
第 4.4 节定义如何信息的移动长-身体被决定。
8 连接
8.1 固执的连接
8.1.1 目的
在~之前固执的连接,一个分开的传输控制协议连接被建立接来每个网址, 增加负荷在