Changeset 697 for draft-ietf-httpbis/latest/p3-payload.xml
- Timestamp:
- 25/09/09 14:43:16 (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p3-payload.xml
r690 r697 983 983 <x:anchor-alias value="media-range"/> 984 984 <t> 985 The request-header field "Accept"can be used to specify certain media985 The "Accept" request-header field can be used to specify certain media 986 986 types which are acceptable for the response. Accept headers can be 987 987 used to indicate that the request is specifically limited to a small … … 1110 1110 <x:anchor-alias value="Accept-Charset-v"/> 1111 1111 <t> 1112 The request-header field "Accept-Charset"can be used to indicate what1112 The "Accept-Charset" request-header field can be used to indicate what 1113 1113 character sets are acceptable for the response. This field allows 1114 1114 clients capable of understanding more comprehensive or special-purpose … … 1155 1155 <x:anchor-alias value="codings"/> 1156 1156 <t> 1157 The request-header field "Accept-Encoding"is similar to Accept, but1157 The "Accept-Encoding" request-header field is similar to Accept, but 1158 1158 restricts the content-codings (<xref target="content.codings"/>) that are acceptable in 1159 1159 the response. … … 1245 1245 <x:anchor-alias value="language-range"/> 1246 1246 <t> 1247 The request-header field "Accept-Language"is similar to Accept, but1247 The "Accept-Language" request-header field is similar to Accept, but 1248 1248 restricts the set of natural languages that are preferred as a 1249 1249 response to the request. Language tags are defined in <xref target="language.tags"/>. … … 1341 1341 <x:anchor-alias value="Content-Encoding-v"/> 1342 1342 <t> 1343 The entity-header field "Content-Encoding"is used as a modifier to the1343 The "Content-Encoding" entity-header field is used as a modifier to the 1344 1344 media-type. When present, its value indicates what additional content 1345 1345 codings have been applied to the entity-body, and thus what decoding … … 1391 1391 <x:anchor-alias value="Content-Language-v"/> 1392 1392 <t> 1393 The entity-header field "Content-Language"describes the natural1393 The "Content-Language" entity-header field describes the natural 1394 1394 language(s) of the intended audience for the enclosed entity. Note 1395 1395 that this might not be equivalent to all the languages used within … … 1445 1445 <x:anchor-alias value="Content-Location-v"/> 1446 1446 <t> 1447 The entity-header field "Content-Location"&MAY; be used to supply the1447 The "Content-Location" entity-header field &MAY; be used to supply the 1448 1448 resource location for the entity enclosed in the message when that 1449 1449 entity is accessible from a location separate from the requested … … 1496 1496 <x:anchor-alias value="Content-MD5-v"/> 1497 1497 <t> 1498 The entity-header field "Content-MD5", as defined in <xref target="RFC1864"/>, is1498 The "Content-MD5" entity-header field, as defined in <xref target="RFC1864"/>, is 1499 1499 an MD5 digest of the entity-body for the purpose of providing an 1500 1500 end-to-end message integrity check (MIC) of the entity-body. (Note: a … … 1573 1573 <x:anchor-alias value="Content-Type-v"/> 1574 1574 <t> 1575 The entity-header field "Content-Type"indicates the media type of the1575 The "Content-Type" entity-header field indicates the media type of the 1576 1576 entity-body sent to the recipient or, in the case of the HEAD method, 1577 1577 the media type that would have been sent had the request been a GET. … … 2675 2675 <x:anchor-alias value="filename-parm"/> 2676 2676 <t> 2677 The Content-Dispositionresponse-header field has been proposed as a2677 The "Content-Disposition" response-header field has been proposed as a 2678 2678 means for the origin server to suggest a default filename if the user 2679 2679 requests that the content is saved to a file. This usage is derived
Note: See TracChangeset
for help on using the changeset viewer.