Changeset 1451 for draft-ietf-httpbis/latest
- Timestamp:
- 20/10/11 08:58:03 (9 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r1450 r1451 359 359 } 360 360 @bottom-center { 361 content: "Expires April 2 0, 2012";361 content: "Expires April 22, 2012"; 362 362 } 363 363 @bottom-right { … … 408 408 <meta name="dct.creator" content="Reschke, J. F."> 409 409 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 410 <meta name="dct.issued" scheme="ISO8601" content="2011-10- 18">410 <meta name="dct.issued" scheme="ISO8601" content="2011-10-20"> 411 411 <meta name="dct.replaces" content="urn:ietf:rfc:2145"> 412 412 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> … … 440 440 </tr> 441 441 <tr> 442 <td class="left">Expires: April 2 0, 2012</td>442 <td class="left">Expires: April 22, 2012</td> 443 443 <td class="right">HP</td> 444 444 </tr> … … 493 493 <tr> 494 494 <td class="left"></td> 495 <td class="right">October 18, 2011</td>495 <td class="right">October 20, 2011</td> 496 496 </tr> 497 497 </tbody> … … 526 526 in progress”. 527 527 </p> 528 <p>This Internet-Draft will expire on April 2 0, 2012.</p>528 <p>This Internet-Draft will expire on April 22, 2012.</p> 529 529 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 530 530 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> -
draft-ietf-httpbis/latest/p2-semantics.html
r1448 r1451 359 359 } 360 360 @bottom-center { 361 content: "Expires April 18, 2012";361 content: "Expires April 22, 2012"; 362 362 } 363 363 @bottom-right { … … 409 409 <meta name="dct.creator" content="Reschke, J. F."> 410 410 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 411 <meta name="dct.issued" scheme="ISO8601" content="2011-10- 16">411 <meta name="dct.issued" scheme="ISO8601" content="2011-10-20"> 412 412 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 413 413 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request header fields, response status codes, and response header fields."> … … 440 440 </tr> 441 441 <tr> 442 <td class="left">Expires: April 18, 2012</td>442 <td class="left">Expires: April 22, 2012</td> 443 443 <td class="right">HP</td> 444 444 </tr> … … 493 493 <tr> 494 494 <td class="left"></td> 495 <td class="right">October 16, 2011</td>495 <td class="right">October 20, 2011</td> 496 496 </tr> 497 497 </tbody> … … 523 523 in progress”. 524 524 </p> 525 <p>This Internet-Draft will expire on April 18, 2012.</p>525 <p>This Internet-Draft will expire on April 22, 2012.</p> 526 526 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 527 527 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 867 867 "http://without-a-comma.example.com/" 868 868 Example-Date-Field: "Sat, 04 May 1996", "Wed, 14 Sep 2005" 869 </pre><p id="rfc.section.3.1.p.7">Many header fields use a format including named parameters (for instance, Content-Type, defined in <a href="p3-payload.html#header.content-type" title="Content-Type">Section 6.8</a> of <a href="#Part3" id="rfc.xref.Part3.1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>). Allowing both unquoted (token) and quoted (quoted-string) syntax for the parameter value enables recipients to use existing869 </pre><p id="rfc.section.3.1.p.7">Many header fields use a format including (case-insensitively) named parameters (for instance, Content-Type, defined in <a href="p3-payload.html#header.content-type" title="Content-Type">Section 6.8</a> of <a href="#Part3" id="rfc.xref.Part3.1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>). Allowing both unquoted (token) and quoted (quoted-string) syntax for the parameter value enables recipients to use existing 870 870 parser components. Also, the meaning of a value ought to be independent of the syntax variant used for it (for an example, 871 871 see the notes on parameter handling for media types in <a href="p3-payload.html#media.types" title="Media Types">Section 2.3</a> of <a href="#Part3" id="rfc.xref.Part3.2"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>). -
draft-ietf-httpbis/latest/p2-semantics.xml
r1448 r1451 524 524 </artwork></figure> 525 525 <t> 526 Many header fields use a format including named parameters (for instance, 527 Content-Type, defined in &header-content-type;). Allowing both unquoted 528 (token) and quoted (quoted-string) syntax for the parameter value enables 529 recipients to use existing parser components. Also, the meaning of a value 530 ought to be independent of the syntax variant used for it (for an example, 531 see the notes on parameter handling for media types in &media-types;). 526 Many header fields use a format including (case-insensitively) named 527 parameters (for instance, Content-Type, defined in &header-content-type;). 528 Allowing both unquoted (token) and quoted (quoted-string) syntax for the 529 parameter value enables recipients to use existing parser components. Also, 530 the meaning of a value ought to be independent of the syntax variant used 531 for it (for an example, see the notes on parameter handling for media types 532 in &media-types;). 532 533 </t> 533 534 <t>
Note: See TracChangeset
for help on using the changeset viewer.