Changeset 2197 for draft-ietf-httpbis/latest
- Timestamp:
- 03/03/13 19:06:21 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 4 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r2195 r2197 449 449 } 450 450 @bottom-center { 451 content: "Expires September 2, 2013";451 content: "Expires September 4, 2013"; 452 452 } 453 453 @bottom-right { … … 491 491 <meta name="dct.creator" content="Reschke, J. F."> 492 492 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 493 <meta name="dct.issued" scheme="ISO8601" content="2013-03-0 1">493 <meta name="dct.issued" scheme="ISO8601" content="2013-03-03"> 494 494 <meta name="dct.replaces" content="urn:ietf:rfc:2145"> 495 495 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> … … 520 520 <tr> 521 521 <td class="left">Intended status: Standards Track</td> 522 <td class="right">March 1, 2013</td>522 <td class="right">March 3, 2013</td> 523 523 </tr> 524 524 <tr> 525 <td class="left">Expires: September 2, 2013</td>525 <td class="left">Expires: September 4, 2013</td> 526 526 <td class="right"></td> 527 527 </tr> … … 551 551 in progress”. 552 552 </p> 553 <p>This Internet-Draft will expire on September 2, 2013.</p>553 <p>This Internet-Draft will expire on September 4, 2013.</p> 554 554 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 555 555 <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1209 1209 the protocol version if their defined semantics allow them to be safely ignored by recipients that do not recognize them. 1210 1210 </p> 1211 <p id="rfc.section.3.2.1.p.2">New HTTP header fields ought to be beregistered with IANA in the Message Header Field Registry, as described in <a href="p2-semantics.html#header.field.registry" title="Header Field Registry">Section 8.3</a> of <a href="#Part2" id="rfc.xref.Part2.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>. A proxy <em class="bcp14">MUST</em> forward unrecognized header fields unless the field-name is listed in the <a href="#header.connection" class="smpl">Connection</a> header field (<a href="#header.connection" id="rfc.xref.header.connection.3" title="Connection">Section 6.1</a>) or the proxy is specifically configured to block, or otherwise transform, such fields. Other recipients <em class="bcp14">SHOULD</em> ignore unrecognized header fields.1211 <p id="rfc.section.3.2.1.p.2">New HTTP header fields ought to be registered with IANA in the Message Header Field Registry, as described in <a href="p2-semantics.html#header.field.registry" title="Header Field Registry">Section 8.3</a> of <a href="#Part2" id="rfc.xref.Part2.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>. A proxy <em class="bcp14">MUST</em> forward unrecognized header fields unless the field-name is listed in the <a href="#header.connection" class="smpl">Connection</a> header field (<a href="#header.connection" id="rfc.xref.header.connection.3" title="Connection">Section 6.1</a>) or the proxy is specifically configured to block, or otherwise transform, such fields. Other recipients <em class="bcp14">SHOULD</em> ignore unrecognized header fields. 1212 1212 </p> 1213 1213 <h3 id="rfc.section.3.2.2"><a href="#rfc.section.3.2.2">3.2.2</a> <a id="field.order" href="#field.order">Field Order</a></h3> -
draft-ietf-httpbis/latest/p1-messaging.xml
r2195 r2197 1199 1199 </t> 1200 1200 <t> 1201 New HTTP header fields ought to be beregistered with IANA in the1201 New HTTP header fields ought to be registered with IANA in the 1202 1202 Message Header Field Registry, as described in &iana-header-registry;. 1203 1203 A proxy &MUST; forward unrecognized header fields unless the -
draft-ietf-httpbis/latest/p2-semantics.html
r2196 r2197 1388 1388 is just as likely to be implemented as a tree of content objects, a programmatic view on various database records, or a gateway 1389 1389 to other information systems. Even when the URI mapping mechanism is tied to a filesystem, an origin server might be configured 1390 to execute the files with the request as input and send the output as the representation, rather th en transfer the files directly.1391 Regardless, only the origin server needs to know how each of its resource identifiers correspond to an implementation, and1390 to execute the files with the request as input and send the output as the representation, rather than transfer the files directly. 1391 Regardless, only the origin server needs to know how each of its resource identifiers corresponds to an implementation, and 1392 1392 how each implementation manages to select and send a current representation of the target resource in a response to GET. 1393 1393 </p> … … 1852 1852 all subtypes of that type. The media-range can include media type parameters that are applicable to that range. 1853 1853 </p> 1854 <p id="rfc.section.5.3.2.p.4">Each media-range might be followed by zero or more applicable media type parameters (e.g., <a href="#charset" class="smpl">charset</a>), an optional "q" parameter for indicating a relative weight (<a href="#quality.values" title="Quality Values">Section 5.3.1</a>), and then zero or more extension parameters. The "q" parameter is necessary if any accept-ext are present, since it acts1855 as a separator between the two parameter sets.1854 <p id="rfc.section.5.3.2.p.4">Each media-range might be followed by zero or more applicable media type parameters (e.g., <a href="#charset" class="smpl">charset</a>), an optional "q" parameter for indicating a relative weight (<a href="#quality.values" title="Quality Values">Section 5.3.1</a>), and then zero or more extension parameters. The "q" parameter is necessary if any extensions (accept-ext) are present, 1855 since it acts as a separator between the two parameter sets. 1856 1856 </p> 1857 1857 <div class="note" id="rfc.section.5.3.2.p.5"> -
draft-ietf-httpbis/latest/p2-semantics.xml
r2196 r2197 1268 1268 other information systems. Even when the URI mapping mechanism is tied to a 1269 1269 filesystem, an origin server might be configured to execute the files with 1270 the request as input and send the output as the representation, rather th en1270 the request as input and send the output as the representation, rather than 1271 1271 transfer the files directly. Regardless, only the origin server needs to 1272 know how each of its resource identifiers correspond to an implementation,1272 know how each of its resource identifiers corresponds to an implementation, 1273 1273 and how each implementation manages to select and send a current 1274 1274 representation of the target resource in a response to GET. … … 2093 2093 parameters (e.g., <x:ref>charset</x:ref>), an optional "q" parameter for 2094 2094 indicating a relative weight (&qvalue;), and then zero or more extension 2095 parameters. The "q" parameter is necessary if any accept-extare present,2095 parameters. The "q" parameter is necessary if any extensions (accept-ext) are present, 2096 2096 since it acts as a separator between the two parameter sets. 2097 2097 </t>
Note: See TracChangeset
for help on using the changeset viewer.