Changeset 1718 for draft-ietf-httpbis


Ignore:
Timestamp:
05/07/12 07:09:14 (9 years ago)
Author:
julian.reschke@…
Message:

regenerate HTML for [1717] (see #326)

File:
1 edited

Legend:

Unmodified
Added
Removed

  • draft-ietf-httpbis/latest/p0-introduction.html

    r1697 r1718  
    251251  margin-left: 0em;
    252252}
     253ul.ind, ul.ind ul {
     254  list-style: none;
     255  margin-left: 1.5em;
     256  padding-left: 0em;
     257  page-break-before: avoid;
     258}
     259ul.ind li {
     260  font-weight: bold;
     261  line-height: 200%;
     262  margin-left: 0em;
     263}
     264ul.ind li li {
     265  font-weight: normal;
     266  line-height: 150%;
     267  margin-left: 0em;
     268}
     269.avoidbreak {
     270  page-break-inside: avoid;
     271}
    253272
    254273.comment {
    … …  
    374393  }
    375394  @bottom-center {
    376        content: "Expires January 2, 2013";
     395       content: "Expires January 6, 2013";
    377396  }
    378397  @bottom-right {
    … …  
    395414      <link rel="Author" href="#rfc.authors">
    396415      <link rel="Copyright" href="#rfc.copyrightnotice">
    397       <link rel="Chapter" title="1 Introduction" href="#rfc.section.1">
    398       <link rel="Chapter" href="#rfc.section.2" title="2 References">
     416      <link rel="Index" href="#rfc.index">
     417      <link rel="Chapter" title="1 Introduction to the HTTP Document Series" href="#rfc.section.1">
     418      <link rel="Chapter" title="2 What is HTTP?" href="#rfc.section.2">
     419      <link rel="Chapter" href="#rfc.section.3" title="3 References">
    399420      <link href="p1-messaging.html" rel="prev">
    400421      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.584, 2012-06-24 15:59:38, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    … …  
    405426      <meta name="dct.creator" content="Reschke, J. F.">
    406427      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p0-introduction-latest">
    407       <meta name="dct.issued" scheme="ISO8601" content="2012-07-01">
    408       <meta name="dct.abstract" content="TODO">
    409       <meta name="description" content="TODO">
     428      <meta name="dct.issued" scheme="ISO8601" content="2012-07-05">
     429      <meta name="dct.abstract" content="This document is the first in a series that, collectively, define the HyperText Transfer Protocol, version 1.1; otherwise known as HTTP/1.1.">
     430      <meta name="description" content="This document is the first in a series that, collectively, define the HyperText Transfer Protocol, version 1.1; otherwise known as HTTP/1.1.">
    410431   </head>
    411432   <body onload="init();">
    … …  
    425446            </tr>
    426447            <tr>
    427                <td class="left">Expires: January 2, 2013</td>
     448               <td class="left">Expires: January 6, 2013</td>
    428449               <td class="right">W3C</td>
    429450            </tr>
    … …  
    446467            <tr>
    447468               <td class="left"></td>
    448                <td class="right">July 1, 2012</td>
     469               <td class="right">July 5, 2012</td>
    449470            </tr>
    450471         </tbody>
    … …  
    452473      <p class="title">HTTP/1.1, part 0: Introduction<br><span class="filename">draft-ietf-httpbis-p0-introduction-latest</span></p>
    453474      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
    454       <p> <span class="comment" id="rfc.comment.1">[<a href="#rfc.comment.1" class="smpl">rfc.comment.1</a>: TODO]</span>
     475      <p>This document is the first in a series that, collectively, define the HyperText Transfer Protocol, version 1.1; otherwise
     476         known as HTTP/1.1.
    455477      </p>
    456478      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
    … …  
    469491         in progress”.
    470492      </p>
    471       <p>This Internet-Draft will expire on January 2, 2013.</p>
     493      <p>This Internet-Draft will expire on January 6, 2013.</p>
    472494      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    473495      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    … …  
    487509      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
    488510      <ul class="toc">
    489          <li>1.&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a></li>
    490          <li>2.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
    491                <li>2.1&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
    492                <li>2.2&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
     511         <li>1.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.1">Introduction to the HTTP Document Series</a></li>
     512         <li>2.&nbsp;&nbsp;&nbsp;<a href="#wat">What is HTTP?</a></li>
     513         <li>3.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
     514               <li>3.1&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
     515               <li>3.2&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
    493516            </ul>
    494517         </li>
    495518         <li><a href="#rfc.authors">Authors' Addresses</a></li>
     519         <li><a href="#rfc.index">Index</a></li>
    496520      </ul>
    497       <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="introduction" href="#introduction">Introduction</a></h1>
    498       <p id="rfc.section.1.p.1"> <span class="comment" id="rfc.comment.2">[<a href="#rfc.comment.2" class="smpl">rfc.comment.2</a>: TODO]</span>
    499       </p>
    500       <h1 id="rfc.references"><a id="rfc.section.2" href="#rfc.section.2">2.</a> References
     521      <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;Introduction to the HTTP Document Series
    501522      </h1>
    502       <h2 id="rfc.references.1"><a href="#rfc.section.2.1" id="rfc.section.2.1">2.1</a> Normative References
     523      <p id="rfc.section.1.p.1">This document is the first in a series that, collectively, define the HyperText Transfer Protocol, version 1.1; otherwise
     524         known as HTTP/1.1.
     525      </p>
     526      <p id="rfc.section.1.p.2">The document series is organised as follows:</p>
     527      <ul>
     528         <li>HTTP/1.1 Introduction - this document</li>
     529         <li><a href="#Part1" id="rfc.xref.Part1.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> HTTP/1.1 Message Parsing and Connection Handling - How to parse a HTTP/1.1 (or below) message, and layer it onto connection-oriented
     530            protocols.
     531         </li>
     532         <li><a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a> HTTP/1.1 Core Semantics - Protocol elements such as methods, status codes, and payload-specific headers. Also includes content
     533            negotiation mechanisms.
     534         </li>
     535         <li><a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a> HTTP/1.1 Conditional Requests - An extension to make requests contingent upon their current state.
     536         </li>
     537         <li><a href="#Part5" id="rfc.xref.Part5.1"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a> HTTP/1.1 Partial Content - An extension to request that only a portion of a response be sent back.
     538         </li>
     539         <li><a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a> HTTP/1.1 Caching - An extension to allow storage and reuse of responses.
     540         </li>
     541         <li><a href="#Part7" id="rfc.xref.Part7.1"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a> HTTP/1.1 Authentication Framework - extension enabling client authentication to proxy and origin servers
     542         </li>
     543      </ul>
     544      <p id="rfc.section.1.p.4">The "core" of HTTP/1.1 is defined by the first two specifications. The remaining specifications in the series are generally
     545         optional, but may be required in some implementation or deployment scenarios; when this is the case, it will be noted.
     546      </p>
     547      <p id="rfc.section.1.p.5">Collectively, these documents obsolete <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>. Note that many other specifications extend and refine the use of HTTP (generally, as protocol extensions, where allowed
     548         by these specifications); they are not considered part of this series, but they are still "part of HTTP".
     549      </p>
     550      <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="wat" href="#wat">What is HTTP?</a></h1>
     551      <p id="rfc.section.2.p.1">The Hypertext Transfer Protocol (HTTP) is an application-level request/response protocol that uses extensible semantics and
     552         MIME-like message payloads for flexible interaction with network-based hypertext information systems. HTTP relies upon the
     553         Uniform Resource Identifier (URI) standard <a href="#RFC3986" id="rfc.xref.RFC3986.1"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a> to indicate the target resource and relationships between resources.
     554      </p>
     555      <p id="rfc.section.2.p.2">HTTP is a generic interface protocol for information systems. It is designed to hide the details of how a service is implemented
     556         by presenting a uniform interface to clients that is independent of the types of resources provided. Likewise, servers do
     557         not need to be aware of each client's purpose: an HTTP request can be considered in isolation rather than being associated
     558         with a specific type of client or a predetermined sequence of application steps. The result is a protocol that can be used
     559         effectively in many different contexts and for which implementations can evolve independently over time.
     560      </p>
     561      <p id="rfc.section.2.p.3">HTTP is also designed for use as an intermediation protocol for translating communication to and from non-HTTP information
     562         systems. HTTP proxies and gateways can provide access to alternative information services by translating their diverse protocols
     563         into a hypertext format that can be viewed and manipulated by clients in the same way as HTTP services.
     564      </p>
     565      <p id="rfc.section.2.p.4">One consequence of HTTP flexibility is that the protocol cannot be defined in terms of what occurs behind the interface. Instead,
     566         we are limited to defining the syntax of communication, the intent of received communication, and the expected behavior of
     567         recipients. If the communication is considered in isolation, then successful actions ought to be reflected in corresponding
     568         changes to the observable interface provided by servers. However, since multiple clients might act in parallel and perhaps
     569         at cross-purposes, we cannot require that such changes be observable beyond the scope of a single response.
     570      </p>
     571      <p id="rfc.section.2.p.5"> <span class="comment" id="rfc.comment.1">[<a href="#rfc.comment.1" class="smpl">rfc.comment.1</a>: TODO: remove corresponding text from p1 Introduction.]</span>
     572      </p>
     573      <h1 id="rfc.references"><a id="rfc.section.3" href="#rfc.section.3">3.</a> References
     574      </h1>
     575      <h2 id="rfc.references.1"><a href="#rfc.section.3.1" id="rfc.section.3.1">3.1</a> Normative References
    503576      </h2>
    504       <table>           
     577      <table>             
    505578         <tr>
    506579            <td class="reference"><b id="Part1">[Part1]</b></td>
    … …  
    533606            </td>
    534607         </tr>
     608         <tr>
     609            <td class="reference"><b id="RFC3986">[RFC3986]</b></td>
     610            <td class="top"><a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R.</a>, and <a href="mailto:LMM@acm.org" title="Adobe Systems Incorporated">L. Masinter</a>, “<a href="http://tools.ietf.org/html/rfc3986">Uniform Resource Identifier (URI): Generic Syntax</a>”, STD&nbsp;66, RFC&nbsp;3986, January&nbsp;2005.
     611            </td>
     612         </tr>
    535613      </table>
    536       <h2 id="rfc.references.2"><a href="#rfc.section.2.2" id="rfc.section.2.2">2.2</a> Informative References
     614      <h2 id="rfc.references.2"><a href="#rfc.section.3.2" id="rfc.section.3.2">3.2</a> Informative References
    537615      </h2>
    538616      <table> 
    … …  
    558636               <span class="n hidden"><span class="family-name">Reschke</span><span class="given-name">Julian F.</span></span></span><span class="org vcardline">greenbytes GmbH</span><span class="adr"><span class="street-address vcardline">Hafenweg 16</span><span class="vcardline"><span class="locality">Muenster</span>, <span class="region">NW</span>&nbsp;<span class="postal-code">48155</span></span><span class="country-name vcardline">Germany</span></span><span class="vcardline">Email: <a href="mailto:julian.reschke@greenbytes.de"><span class="email">julian.reschke@greenbytes.de</span></a></span><span class="vcardline">URI: <a href="http://greenbytes.de/tech/webdav/" class="url">http://greenbytes.de/tech/webdav/</a></span></address>
    559637      </div>
     638      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
     639      <p class="noprint"><a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a>
     640      </p>
     641      <div class="print2col">
     642         <ul class="ind">
     643            <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
     644                  <li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1</a>, <a href="#Part1"><b>3.1</b></a></li>
     645                  <li><em>Part2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">1</a>, <a href="#Part2"><b>3.1</b></a></li>
     646                  <li><em>Part4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">1</a>, <a href="#Part4"><b>3.1</b></a></li>
     647                  <li><em>Part5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.1">1</a>, <a href="#Part5"><b>3.1</b></a></li>
     648                  <li><em>Part6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">1</a>, <a href="#Part6"><b>3.1</b></a></li>
     649                  <li><em>Part7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.1">1</a>, <a href="#Part7"><b>3.1</b></a></li>
     650               </ul>
     651            </li>
     652            <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul>
     653                  <li><em>RFC2616</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1">1</a>, <a href="#RFC2616"><b>3.2</b></a></li>
     654                  <li><em>RFC3986</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.1">2</a>, <a href="#RFC3986"><b>3.1</b></a></li>
     655               </ul>
     656            </li>
     657         </ul>
     658      </div>
    560659   </body>
    561660</html>
Note: See TracChangeset for help on using the changeset viewer.