Changeset 1373 for draft-ietf-httpbis/latest
- Timestamp:
- 03/08/11 15:57:21 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 14 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r1371 r1373 503 503 <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information 504 504 systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 1 of the 505 seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 506 1 provides an overview of HTTP and its associated terminology, defines the "http" and "https" Uniform Resource Identifier 505 seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. 506 </p> 507 <p>Part 1 provides an overview of HTTP and its associated terminology, defines the "http" and "https" Uniform Resource Identifier 507 508 (URI) schemes, defines the generic message syntax and parsing requirements for HTTP message frames, and describes general 508 509 security concerns for implementations. -
draft-ietf-httpbis/latest/p1-messaging.xml
r1370 r1373 198 198 <abstract> 199 199 <t> 200 The Hypertext Transfer Protocol (HTTP) is an application-level 201 protocol for distributed, collaborative, hypertext information 202 systems. HTTP has been in use by the World Wide Web global information 203 initiative since 1990. This document is Part 1 of the seven-part specification 204 that defines the protocol referred to as "HTTP/1.1" and, taken together, 205 obsoletes RFC 2616. Part 1 provides an overview of HTTP and 206 its associated terminology, defines the "http" and "https" Uniform 207 Resource Identifier (URI) schemes, defines the generic message syntax 208 and parsing requirements for HTTP message frames, and describes 209 general security concerns for implementations. 200 The Hypertext Transfer Protocol (HTTP) is an application-level protocol for 201 distributed, collaborative, hypertext information systems. HTTP has been in 202 use by the World Wide Web global information initiative since 1990. This 203 document is Part 1 of the seven-part specification that defines the protocol 204 referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. 205 </t> 206 <t> 207 Part 1 provides an overview of HTTP and its associated terminology, defines 208 the "http" and "https" Uniform Resource Identifier (URI) schemes, defines 209 the generic message syntax and parsing requirements for HTTP message frames, 210 and describes general security concerns for implementations. 210 211 </t> 211 212 </abstract> -
draft-ietf-httpbis/latest/p2-semantics.html
r1368 r1373 359 359 } 360 360 @bottom-center { 361 content: "Expires February 2, 2012";361 content: "Expires February 4, 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-08-0 1">411 <meta name="dct.issued" scheme="ISO8601" content="2011-08-03"> 412 412 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 413 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hyper mediainformation 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.">414 <meta name="description" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hyper mediainformation 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.">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."> 414 <meta name="description" 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."> 415 415 </head> 416 416 <body> … … 440 440 </tr> 441 441 <tr> 442 <td class="left">Expires: February 2, 2012</td>442 <td class="left">Expires: February 4, 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">August 1, 2011</td>495 <td class="right">August 3, 2011</td> 496 496 </tr> 497 497 </tbody> … … 499 499 <p class="title">HTTP/1.1, part 2: Message Semantics<br><span class="filename">draft-ietf-httpbis-p2-semantics-latest</span></p> 500 500 <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 501 <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hyper mediainformation501 <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information 502 502 systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the 503 seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 504 2 defines the semantics of HTTP messages as expressed by request methods, request header fields, response status codes, and 505 response header fields. 503 seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. 504 </p> 505 <p>Part 2 defines the semantics of HTTP messages as expressed by request methods, request header fields, response status codes, 506 and response header fields. 506 507 </p> 507 508 <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> … … 522 523 in progress”. 523 524 </p> 524 <p>This Internet-Draft will expire on February 2, 2012.</p>525 <p>This Internet-Draft will expire on February 4, 2012.</p> 525 526 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 526 527 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> -
draft-ietf-httpbis/latest/p2-semantics.xml
r1368 r1373 243 243 <abstract> 244 244 <t> 245 The Hypertext Transfer Protocol (HTTP) is an application-level 246 protocol for distributed, collaborative, hypermedia information 247 systems. HTTP has been in use by the World Wide Web global information 248 initiative since 1990. This document is Part 2 of the seven-part specification 249 that defines the protocol referred to as "HTTP/1.1" and, taken together, 250 obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages 251 as expressed by request methods, request header fields, response status codes, 252 and response header fields. 245 The Hypertext Transfer Protocol (HTTP) is an application-level protocol for 246 distributed, collaborative, hypertext information systems. HTTP has been in 247 use by the World Wide Web global information initiative since 1990. This 248 document is Part 2 of the seven-part specification that defines the protocol 249 referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. 250 </t> 251 <t> 252 Part 2 defines the semantics of HTTP messages as expressed by request 253 methods, request header fields, response status codes, and response header 254 fields. 253 255 </t> 254 256 </abstract> -
draft-ietf-httpbis/latest/p3-payload.html
r1368 r1373 359 359 } 360 360 @bottom-center { 361 content: "Expires February 2, 2012";361 content: "Expires February 4, 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-p3-payload-latest"> 410 <meta name="dct.issued" scheme="ISO8601" content="2011-08-0 1">410 <meta name="dct.issued" scheme="ISO8601" content="2011-08-03"> 411 411 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 412 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hyper mediainformation systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 3 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 3 defines HTTP message content, metadata, and content negotiation.">413 <meta name="description" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hyper mediainformation systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 3 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 3 defines HTTP message content, metadata, and content negotiation.">412 <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 3 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 3 defines HTTP message content, metadata, and content negotiation."> 413 <meta name="description" 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 3 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 3 defines HTTP message content, metadata, and content negotiation."> 414 414 </head> 415 415 <body> … … 434 434 </tr> 435 435 <tr> 436 <td class="left">Expires: February 2, 2012</td>436 <td class="left">Expires: February 4, 2012</td> 437 437 <td class="right">J. Mogul</td> 438 438 </tr> … … 491 491 <tr> 492 492 <td class="left"></td> 493 <td class="right">August 1, 2011</td>493 <td class="right">August 3, 2011</td> 494 494 </tr> 495 495 </tbody> … … 497 497 <p class="title">HTTP/1.1, part 3: Message Payload and Content Negotiation<br><span class="filename">draft-ietf-httpbis-p3-payload-latest</span></p> 498 498 <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 499 <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hyper mediainformation499 <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information 500 500 systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 3 of the 501 seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part502 3 defines HTTP message content, metadata, and content negotiation.503 < /p>501 seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. 502 </p> 503 <p>Part 3 defines HTTP message content, metadata, and content negotiation.</p> 504 504 <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> 505 505 <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), which is archived … … 519 519 in progress”. 520 520 </p> 521 <p>This Internet-Draft will expire on February 2, 2012.</p>521 <p>This Internet-Draft will expire on February 4, 2012.</p> 522 522 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 523 523 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> -
draft-ietf-httpbis/latest/p3-payload.xml
r1368 r1373 200 200 <abstract> 201 201 <t> 202 The Hypertext Transfer Protocol (HTTP) is an application-level 203 protocol for distributed, collaborative, hypermedia information 204 systems. HTTP has been in use by the World Wide Web global information 205 initiative since 1990. This document is Part 3 of the seven-part specification 206 that defines the protocol referred to as "HTTP/1.1" and, taken together, 207 obsoletes RFC 2616. Part 3 defines HTTP message content, 208 metadata, and content negotiation. 202 The Hypertext Transfer Protocol (HTTP) is an application-level protocol for 203 distributed, collaborative, hypertext information systems. HTTP has been in 204 use by the World Wide Web global information initiative since 1990. This 205 document is Part 3 of the seven-part specification that defines the protocol 206 referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. 207 </t> 208 <t> 209 Part 3 defines HTTP message content, metadata, and content negotiation. 209 210 </t> 210 211 </abstract> -
draft-ietf-httpbis/latest/p4-conditional.html
r1368 r1373 359 359 } 360 360 @bottom-center { 361 content: "Expires February 2, 2012";361 content: "Expires February 4, 2012"; 362 362 } 363 363 @bottom-right { … … 404 404 <meta name="dct.creator" content="Reschke, J. F."> 405 405 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest"> 406 <meta name="dct.issued" scheme="ISO8601" content="2011-08-0 1">406 <meta name="dct.issued" scheme="ISO8601" content="2011-08-03"> 407 407 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 408 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hyper mediainformation systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 4 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 4 defines request header fields for indicating conditional requests and the rules for constructing responses to those requests.">409 <meta name="description" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hyper mediainformation systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 4 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 4 defines request header fields for indicating conditional requests and the rules for constructing responses to those requests.">408 <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 4 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 4 defines request header fields for indicating conditional requests and the rules for constructing responses to those requests."> 409 <meta name="description" 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 4 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 4 defines request header fields for indicating conditional requests and the rules for constructing responses to those requests."> 410 410 </head> 411 411 <body> … … 430 430 </tr> 431 431 <tr> 432 <td class="left">Expires: February 2, 2012</td>432 <td class="left">Expires: February 4, 2012</td> 433 433 <td class="right">J. Mogul</td> 434 434 </tr> … … 487 487 <tr> 488 488 <td class="left"></td> 489 <td class="right">August 1, 2011</td>489 <td class="right">August 3, 2011</td> 490 490 </tr> 491 491 </tbody> … … 493 493 <p class="title">HTTP/1.1, part 4: Conditional Requests<br><span class="filename">draft-ietf-httpbis-p4-conditional-latest</span></p> 494 494 <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 495 <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hyper mediainformation495 <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information 496 496 systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 4 of the 497 seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 498 4 defines request header fields for indicating conditional requests and the rules for constructing responses to those requests. 497 seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. 498 </p> 499 <p>Part 4 defines request header fields for indicating conditional requests and the rules for constructing responses to those 500 requests. 499 501 </p> 500 502 <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> … … 515 517 in progress”. 516 518 </p> 517 <p>This Internet-Draft will expire on February 2, 2012.</p>519 <p>This Internet-Draft will expire on February 4, 2012.</p> 518 520 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 519 521 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> -
draft-ietf-httpbis/latest/p4-conditional.xml
r1368 r1373 190 190 <abstract> 191 191 <t> 192 The Hypertext Transfer Protocol (HTTP) is an application-level 193 protocol for distributed, collaborative, hypermedia information 194 systems. HTTP has been in use by the World Wide Web global information 195 initiative since 1990. This document is Part 4 of the seven-part specification 196 that defines the protocol referred to as "HTTP/1.1" and, taken together, 197 obsoletes RFC 2616. Part 4 defines request header fields for 198 indicating conditional requests and the rules for constructing responses 199 to those requests. 192 The Hypertext Transfer Protocol (HTTP) is an application-level protocol for 193 distributed, collaborative, hypertext information systems. HTTP has been in 194 use by the World Wide Web global information initiative since 1990. This 195 document is Part 4 of the seven-part specification that defines the protocol 196 referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. 197 </t> 198 <t> 199 Part 4 defines request header fields for indicating conditional requests and 200 the rules for constructing responses to those requests. 200 201 </t> 201 202 </abstract> -
draft-ietf-httpbis/latest/p5-range.html
r1368 r1373 359 359 } 360 360 @bottom-center { 361 content: "Expires February 2, 2012";361 content: "Expires February 4, 2012"; 362 362 } 363 363 @bottom-right { … … 406 406 <meta name="dct.creator" content="Reschke, J. F."> 407 407 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest"> 408 <meta name="dct.issued" scheme="ISO8601" content="2011-08-0 1">408 <meta name="dct.issued" scheme="ISO8601" content="2011-08-03"> 409 409 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 410 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hyper mediainformation systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 5 defines range-specific requests and the rules for constructing and combining responses to those requests.">411 <meta name="description" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hyper mediainformation systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 5 defines range-specific requests and the rules for constructing and combining responses to those requests.">410 <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 5 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 5 defines range-specific requests and the rules for constructing and combining responses to those requests."> 411 <meta name="description" 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 5 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 5 defines range-specific requests and the rules for constructing and combining responses to those requests."> 412 412 </head> 413 413 <body> … … 432 432 </tr> 433 433 <tr> 434 <td class="left">Expires: February 2, 2012</td>434 <td class="left">Expires: February 4, 2012</td> 435 435 <td class="right">J. Mogul</td> 436 436 </tr> … … 489 489 <tr> 490 490 <td class="left"></td> 491 <td class="right">August 1, 2011</td>491 <td class="right">August 3, 2011</td> 492 492 </tr> 493 493 </tbody> … … 495 495 <p class="title">HTTP/1.1, part 5: Range Requests and Partial Responses<br><span class="filename">draft-ietf-httpbis-p5-range-latest</span></p> 496 496 <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 497 <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hyper mediainformation497 <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information 498 498 systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the 499 seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part500 5 defines range-specific requests and the rules for constructing and combining responses to those requests.501 < /p>499 seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. 500 </p> 501 <p>Part 5 defines range-specific requests and the rules for constructing and combining responses to those requests.</p> 502 502 <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> 503 503 <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), which is archived … … 517 517 in progress”. 518 518 </p> 519 <p>This Internet-Draft will expire on February 2, 2012.</p>519 <p>This Internet-Draft will expire on February 4, 2012.</p> 520 520 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 521 521 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> -
draft-ietf-httpbis/latest/p5-range.xml
r1368 r1373 183 183 <abstract> 184 184 <t> 185 The Hypertext Transfer Protocol (HTTP) is an application-level 186 protocol for distributed, collaborative, hypermedia information 187 systems. HTTP has been in use by the World Wide Web global information 188 initiative since 1990. This document is Part 5 of the seven-part specification 189 that defines the protocol referred to as "HTTP/1.1" and, taken together, 190 obsoletes RFC 2616. Part 5 defines range-specific requests and 191 the rules for constructing and combining responses to those requests. 185 The Hypertext Transfer Protocol (HTTP) is an application-level protocol for 186 distributed, collaborative, hypertext information systems. HTTP has been in 187 use by the World Wide Web global information initiative since 1990. This 188 document is Part 5 of the seven-part specification that defines the protocol 189 referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. 190 </t> 191 <t> 192 Part 5 defines range-specific requests and the rules for constructing and 193 combining responses to those requests. 192 194 </t> 193 195 </abstract> -
draft-ietf-httpbis/latest/p6-cache.html
r1368 r1373 362 362 } 363 363 @bottom-center { 364 content: "Expires February 2, 2012";364 content: "Expires February 4, 2012"; 365 365 } 366 366 @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-p6-cache-latest"> 410 <meta name="dct.issued" scheme="ISO8601" content="2011-08-0 1">410 <meta name="dct.issued" scheme="ISO8601" content="2011-08-03"> 411 411 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 412 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hyper media information systems. This document is Part 6 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 6 defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.">413 <meta name="description" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hyper media information systems. This document is Part 6 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 6 defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.">412 <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 6 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 6 defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages."> 413 <meta name="description" 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 6 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 6 defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages."> 414 414 </head> 415 415 <body> … … 434 434 </tr> 435 435 <tr> 436 <td class="left">Expires: February 2, 2012</td>436 <td class="left">Expires: February 4, 2012</td> 437 437 <td class="right">J. Mogul</td> 438 438 </tr> … … 495 495 <tr> 496 496 <td class="left"></td> 497 <td class="right">August 1, 2011</td>497 <td class="right">August 3, 2011</td> 498 498 </tr> 499 499 </tbody> … … 501 501 <p class="title">HTTP/1.1, part 6: Caching<br><span class="filename">draft-ietf-httpbis-p6-cache-latest</span></p> 502 502 <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 503 <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information 504 systems. This document is Part 6 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, 505 taken together, obsoletes RFC 2616. Part 6 defines requirements on HTTP caches and the associated header fields that control 506 cache behavior or indicate cacheable response messages. 503 <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information 504 systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 6 of the 505 seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. 506 </p> 507 <p>Part 6 defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable 508 response messages. 507 509 </p> 508 510 <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> … … 523 525 in progress”. 524 526 </p> 525 <p>This Internet-Draft will expire on February 2, 2012.</p>527 <p>This Internet-Draft will expire on February 4, 2012.</p> 526 528 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 527 529 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> -
draft-ietf-httpbis/latest/p6-cache.xml
r1368 r1373 202 202 <t> 203 203 The Hypertext Transfer Protocol (HTTP) is an application-level protocol for 204 distributed, collaborative, hypermedia information systems. This document 205 is Part 6 of the seven-part specification that defines the protocol 206 referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 6 207 defines requirements on HTTP caches and the associated header fields that 208 control cache behavior or indicate cacheable response messages. 204 distributed, collaborative, hypertext information systems. HTTP has been in 205 use by the World Wide Web global information initiative since 1990. This 206 document is Part 6 of the seven-part specification that defines the protocol 207 referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. 208 </t> 209 <t> 210 Part 6 defines requirements on HTTP caches and the associated header fields 211 that control cache behavior or indicate cacheable response messages. 209 212 </t> 210 213 </abstract> -
draft-ietf-httpbis/latest/p7-auth.html
r1371 r1373 406 406 <meta name="dct.issued" scheme="ISO8601" content="2011-08-03"> 407 407 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 408 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 7 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 7 defines HTTP Authentication.">409 <meta name="description" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 7 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 7 defines HTTP Authentication.">408 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 7 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 7 defines the HTTP Authentication framework."> 409 <meta name="description" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 7 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 7 defines the HTTP Authentication framework."> 410 410 </head> 411 411 <body> … … 496 496 <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information 497 497 systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 7 of the 498 seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part499 7 defines HTTP Authentication.500 < /p>498 seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. 499 </p> 500 <p>Part 7 defines the HTTP Authentication framework.</p> 501 501 <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> 502 502 <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), which is archived -
draft-ietf-httpbis/latest/p7-auth.xml
r1371 r1373 184 184 <abstract> 185 185 <t> 186 The Hypertext Transfer Protocol (HTTP) is an application-level 187 protocol for distributed, collaborative, hypermedia information 188 systems. HTTP has been in use by the World Wide Web global information 189 initiative since 1990. This document is Part 7 of the seven-part specification 190 that defines the protocol referred to as "HTTP/1.1" and, taken together, 191 obsoletes RFC 2616. Part 7 defines HTTP Authentication. 186 The Hypertext Transfer Protocol (HTTP) is an application-level protocol for 187 distributed, collaborative, hypermedia information systems. HTTP has been in 188 use by the World Wide Web global information initiative since 1990. This 189 document is Part 7 of the seven-part specification that defines the protocol 190 referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. 191 </t> 192 <t> 193 Part 7 defines the HTTP Authentication framework. 192 194 </t> 193 195 </abstract>
Note: See TracChangeset
for help on using the changeset viewer.