Changeset 866 for draft-ietf-httpbis/latest/p3-payload.xml
- Timestamp:
- 22/07/10 09:06:27 (12 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p3-payload.xml
r864 r866 465 465 <t> 466 466 Content coding values indicate an encoding transformation that has 467 been or can be applied to a n entity. Content codings are primarily468 used to allow a documentto be compressed or otherwise usefully467 been or can be applied to a representation. Content codings are primarily 468 used to allow a representation to be compressed or otherwise usefully 469 469 transformed without losing the identity of its underlying media type 470 and without loss of information. Frequently, the entityis stored in470 and without loss of information. Frequently, the representation is stored in 471 471 coded form, transmitted directly, and only decoded by the recipient. 472 472 </t> … … 707 707 <section title="Entity" anchor="entity"> 708 708 <t> 709 Request and Response messages &MAY; transfer a n entityif not otherwise710 restricted by the request method or response status code. A n entity711 consists of entity-header fields and a n entity-body, although some709 Request and Response messages &MAY; transfer a representation if not otherwise 710 restricted by the request method or response status code. A representation 711 consists of entity-header fields and a representation body, although some 712 712 responses will only include the entity-headers. 713 713 </t> 714 714 <t> 715 715 In this section, both sender and recipient refer to either the client 716 or the server, depending on who sends and who receives the entity.716 or the server, depending on who sends and who receives the message. 717 717 </t> 718 718 … … 966 966 <t> 967 967 For entity-header fields, both sender and recipient refer to either the 968 client or the server, depending on who sends and who receives the entity.968 client or the server, depending on who sends and who receives the message. 969 969 </t> 970 970 … … 1049 1049 Verbally, this would be interpreted as "text/html and text/x-c are 1050 1050 the preferred media types, but if they do not exist, then send the 1051 text/x-dvi entity, and if that does not exist, send the text/plain1052 entity."1051 text/x-dvi representation, and if that does not exist, send the text/plain 1052 representation." 1053 1053 </t> 1054 1054 <t> … … 1311 1311 <t> 1312 1312 The "Content-Encoding" entity-header field indicates what content-codings 1313 have been applied to the entity-body, and thus what decoding mechanisms1313 have been applied to the representation, and thus what decoding mechanisms 1314 1314 must be applied in order to obtain the media-type referenced by the 1315 1315 Content-Type header field. Content-Encoding is primarily used to allow a 1316 documentto be compressed without losing the identity of its underlying1316 representation to be compressed without losing the identity of its underlying 1317 1317 media type. 1318 1318 </t> … … 1328 1328 </artwork></figure> 1329 1329 <t> 1330 The content-coding is a characteristic of the entity identified by1331 the Effective Request URI (&effective-request-uri;). Typically, the entity-body is stored with this1330 The content-coding is a characteristic of the representation. 1331 Typically, the representation body is stored with this 1332 1332 encoding and is only decoded before rendering or analogous usage. 1333 1333 However, a non-transparent proxy &MAY; modify the content-coding if the … … 1336 1336 </t> 1337 1337 <t> 1338 If the content-coding of an entity is not "identity", then the 1339 response &MUST; include a Content-Encoding entity-header (<xref target="header.content-encoding"/>) 1338 If the content-coding of a representation is not "identity", then the 1339 representation metadata &MUST; include a Content-Encoding header 1340 field (<xref target="header.content-encoding"/>) 1340 1341 that lists the non-identity content-coding(s) used. 1341 1342 </t> … … 1346 1347 </t> 1347 1348 <t> 1348 If multiple encodings have been applied to a n entity, the content1349 If multiple encodings have been applied to a representation, the content 1349 1350 codings &MUST; be listed in the order in which they were applied. 1350 1351 Additional information about the encoding parameters &MAY; be provided 1351 by other entity-header fields not defined by this specification.1352 by other header fields not defined by this specification. 1352 1353 </t> 1353 1354 </section> … … 1360 1361 <t> 1361 1362 The "Content-Language" entity-header field describes the natural 1362 language(s) of the intended audience for the entity. Note that this might1363 language(s) of the intended audience for the representation. Note that this might 1363 1364 not be equivalent to all the languages used within the entity-body. 1364 1365 </t> … … 1370 1371 Language tags are defined in <xref target="language.tags"/>. The primary purpose of 1371 1372 Content-Language is to allow a user to identify and differentiate 1372 entities according to the user's own preferred language. Thus, if the1373 representations according to the user's own preferred language. Thus, if the 1373 1374 body content is intended only for a Danish-literate audience, the 1374 1375 appropriate field is … … 1393 1394 </artwork></figure> 1394 1395 <t> 1395 However, just because multiple languages are present within a n entity1396 However, just because multiple languages are present within a representation 1396 1397 does not mean that it is intended for multiple linguistic audiences. 1397 1398 An example would be a beginner's language primer, such as "A First … … 1526 1527 any transfer-encoding applied to the message-body. If the message is 1527 1528 received with a transfer-encoding, that encoding &MUST; be removed 1528 prior to checking the Content-MD5 value against the received entity.1529 prior to checking the Content-MD5 value against the received representation. 1529 1530 </t> 1530 1531 <t>
Note: See TracChangeset
for help on using the changeset viewer.