13/11/08 03:04:45 (13 years ago)

expand on when to use HTTP

1 edited


  • draft-ietf-httpbis/latest-roy/p1-messaging.html

    r350 r361  
    533533                     <li class="tocline1">2.1.1&nbsp;&nbsp;&nbsp;<a href="#http.uri">http URI scheme</a></li>
    534534                     <li class="tocline1">2.1.2&nbsp;&nbsp;&nbsp;<a href="#uri.comparison">URI Comparison</a></li>
     535                     <li class="tocline1">2.1.3&nbsp;&nbsp;&nbsp;<a href="#scheme.aliases">Scheme aliases considered harmful</a></li>
    535536                  </ul>
    536537               </li>
    537538               <li class="tocline1">2.2&nbsp;&nbsp;&nbsp;<a href="#intro.overall.operation">Overall Operation</a></li>
     539               <li class="tocline1">2.3&nbsp;&nbsp;&nbsp;<a href="#http.proxy">Use of HTTP for proxy communication</a></li>
     540               <li class="tocline1">2.4&nbsp;&nbsp;&nbsp;<a href="#http.intercept">Interception of HTTP for access control</a></li>
     541               <li class="tocline1">2.5&nbsp;&nbsp;&nbsp;<a href="#http.others">Use of HTTP by other protocols</a></li>
     542               <li class="tocline1">2.6&nbsp;&nbsp;&nbsp;<a href="#http.media">Use of HTTP by media type specification</a></li>
    538543            </ul>
    539544         </li>
    793798  <a href="#abnf.dependencies" class="smpl">Warning</a>         = &lt;Warning, defined in <a href="#Part6" id="rfc.xref.Part6.3"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.warning" title="Warning">Section 16.6</a>&gt;
    794799</pre><h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="when" href="#when">When to use HTTP</a></h1>
     800      <p id="rfc.section.2.p.1">HTTP is a generic interface protocol for informations systems. It is designed to hide the details of how a service is implemented
     801         by presenting a uniform interface to clients that is independent of the types of resources provided. Likewise, servers do
     802         not need to be aware of the client's purpose: each HTTP request can be considered independently rather than being associated
     803         with a specific type of client or a predetermined sequence of application steps. The result is a protocol that can be used
     804         effectively in many different contexts and for which implementations can evolve independently over time.
     805      </p>
     806      <p id="rfc.section.2.p.2">One consequence of HTTP flexibility is that we cannot define the protocol in terms of how to implement it behind the interface.
     807         Instead, we are limited to restricting the syntax of communication, defining the intent of received communication, and the
     808         expected behavior of recipients. If the communication is considered in isolation, then successful actions should be reflected
     809         in the observable interface provided by servers. However, since many clients are potentially acting in parallel and perhaps
     810         at cross-purposes, it would be meaningless to require that such behavior be observable.
     811      </p>
     812      <p id="rfc.section.2.p.3">This section describes the most common contexts in which a user agent is encouraged or instructed to use HTTP for communication
     813         and how such contexts differ in terms of their resulting communication.
     814      </p>
    795815      <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a id="uri" href="#uri">Uniform Resource Identifiers</a></h2>
    796816      <p id="rfc.section.2.1.p.1">Uniform Resource Identifiers (URIs) <a href="#RFC3986" id="rfc.xref.RFC3986.2"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a> are used in HTTP to indicate the target of a request and to identify additional resources related to that resource, the request,
    849869   http://EXAMPLE.com/%7Esmith/home.html
    850870   http://EXAMPLE.com:/%7esmith/home.html
    851 </pre><h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a>&nbsp;<a id="intro.overall.operation" href="#intro.overall.operation">Overall Operation</a></h2>
     871</pre><h3 id="rfc.section.2.1.3"><a href="#rfc.section.2.1.3">2.1.3</a>&nbsp;<a id="scheme.aliases" href="#scheme.aliases">Scheme aliases considered harmful</a></h3>
     872      <h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a>&nbsp;<a id="intro.overall.operation" href="#intro.overall.operation">Overall Operation</a></h2>
    852873      <p id="rfc.section.2.2.p.1">HTTP is a request/response protocol. A client sends a request to the server in the form of a request method, URI, and protocol
    853874         version, followed by a MIME-like message containing request modifiers, client information, and possible body content over
    908929         be used for one or more request/response exchanges, although connections may be closed for a variety of reasons (see <a href="#persistent.connections" title="Persistent Connections">Section&nbsp;7.1</a>).
    909930      </p>
     931      <h2 id="rfc.section.2.3"><a href="#rfc.section.2.3">2.3</a>&nbsp;<a id="http.proxy" href="#http.proxy">Use of HTTP for proxy communication</a></h2>
     932      <p id="rfc.section.2.3.p.1">Configured to use HTTP to proxy HTTP or other protocols.</p>
     933      <h2 id="rfc.section.2.4"><a href="#rfc.section.2.4">2.4</a>&nbsp;<a id="http.intercept" href="#http.intercept">Interception of HTTP for access control</a></h2>
     934      <p id="rfc.section.2.4.p.1">Interception of HTTP traffic for initiating access control.</p>
     935      <h2 id="rfc.section.2.5"><a href="#rfc.section.2.5">2.5</a>&nbsp;<a id="http.others" href="#http.others">Use of HTTP by other protocols</a></h2>
     936      <p id="rfc.section.2.5.p.1">Profiles of HTTP defined by other protocol. Extensions of HTTP like WebDAV.</p>
     937      <h2 id="rfc.section.2.6"><a href="#rfc.section.2.6">2.6</a>&nbsp;<a id="http.media" href="#http.media">Use of HTTP by media type specification</a></h2>
     938      <p id="rfc.section.2.6.p.1">Instructions on composing HTTP requests via hypertext formats.</p>
    910939      <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="protocol.parameters" href="#protocol.parameters">Protocol Parameters</a></h1>
    911940      <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a id="http.version" href="#http.version">HTTP Version</a></h2>
Note: See TracChangeset for help on using the changeset viewer.