Source: https://trac.ietf.org/trac/httpbis/changeset/413/draft-ietf-httpbis
Timestamp: 2020-02-28 15:22:43
Document Index: 241938439

Matched Legal Cases: ['art6', 'art6', 'art 6', 'art6', 'art3', 'art3', 'art 3', 'art3', 'art3', 'art3', 'art 3', 'art3', 'art3', 'art3', 'art 3', 'art3', 'art3', 'art3', 'art 3', 'art3', 'art3', 'art3', 'art 3', 'art3', 'art3', 'art3', 'art 3', 'art3', 'art3', 'art3', 'art3', 'art3', 'art3', 'art3', 'art3', 'art3', 'art3', 'art3', 'art3', 'art3', 'art3']

Changeset 413 for draft-ietf-httpbis – Hypertext Transfer Protocol Wiki
Changeset 413 for draft-ietf-httpbis
18/11/08 16:53:23 (11 years ago)
Resolve #52: Sort Terminology entries (closes #52)
p1-messaging.xml (modified) (7 diffs)
<h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="terminology" href="#terminology">Terminology</a></h1>
<p id="rfc.section.C.p.1">This specification uses a number of terms to refer to the roles played by participants in, and objects of, the HTTP communication.</p>
<p id="rfc.section.C.p.2"> <span id="rfc.iref.c.3"></span> <dfn>connection</dfn>
<p id="rfc.section.C.p.2"> <span id="rfc.iref.c.3"></span> <dfn>cache</dfn>
<p id="rfc.section.C.p.3"> <span id="rfc.iref.c.4"></span> <dfn>cacheable</dfn>
The rules for determining the cacheability of HTTP responses are defined in <a href="p6-cache.html#caching" title="Introduction">Section 1</a> of <a href="#Part6" id="rfc.xref.Part6.9"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>. Even if a resource is cacheable, there may be additional constraints on whether a cache can use the cached copy for a particular
<p id="rfc.section.C.p.4"> <span id="rfc.iref.c.5"></span> <dfn>client</dfn>
<dd>A program that establishes connections for the purpose of sending requests.</dd>
<p id="rfc.section.C.p.5"> <span id="rfc.iref.c.6"></span> <dfn>connection</dfn>
<dd>A transport layer virtual circuit established between two programs for the purpose of communication.</dd>
<p id="rfc.section.C.p.3"> <span id="rfc.iref.m.4"></span> <dfn>message</dfn>
<p id="rfc.section.C.p.6"> <span id="rfc.iref.c.7"></span> <dfn>content negotiation</dfn>
<dd>The mechanism for selecting the appropriate representation when servicing a request, as described in <a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 5</a> of <a href="#Part3" id="rfc.xref.Part3.13"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. The representation of entities in any response can be negotiated (including error responses).
<p id="rfc.section.C.p.7"> <span id="rfc.iref.e.1"></span> <dfn>entity</dfn>
<dd>The information transferred as the payload of a request or response. An entity consists of metainformation in the form of
entity-header fields and content in the form of an entity-body, as described in <a href="p3-payload.html#entity" title="Entity">Section 4</a> of <a href="#Part3" id="rfc.xref.Part3.14"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>.
<p id="rfc.section.C.p.8"> <span id="rfc.iref.g.107"></span> <dfn>gateway</dfn>
<dd>A server which acts as an intermediary for some other server. Unlike a proxy, a gateway receives requests as if it were the
origin server for the requested resource; the requesting client may not be aware that it is communicating with a gateway.
<p id="rfc.section.C.p.9"> <span id="rfc.iref.i.1"></span> <span id="rfc.iref.o.1"></span> <dfn>inbound</dfn>/<dfn>outbound</dfn>
<dd>Inbound and outbound refer to the request and response paths for messages: "inbound" means "traveling toward the origin server",
<p id="rfc.section.C.p.10"> <span id="rfc.iref.m.4"></span> <dfn>message</dfn>
<p id="rfc.section.C.p.4"> <span id="rfc.iref.r.1"></span> <dfn>request</dfn>
<dd>An HTTP request message, as defined in <a href="#request" title="Request">Section&nbsp;5</a>.
<p id="rfc.section.C.p.5"> <span id="rfc.iref.r.2"></span> <dfn>response</dfn>
<dd>An HTTP response message, as defined in <a href="#response" title="Response">Section&nbsp;6</a>.
<p id="rfc.section.C.p.6"> <span id="rfc.iref.r.3"></span> <dfn>resource</dfn>
<dd>A network data object or service that can be identified by a URI, as defined in <a href="#uri" title="Uniform Resource Identifiers">Section&nbsp;2.1</a>. Resources may be available in multiple representations (e.g. multiple languages, data formats, size, and resolutions) or
vary in other ways.
entity-header fields and content in the form of an entity-body, as described in <a href="p3-payload.html#entity" title="Entity">Section 4</a> of <a href="#Part3" id="rfc.xref.Part3.13"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>.
<p id="rfc.section.C.p.8"> <span id="rfc.iref.r.4"></span> <dfn>representation</dfn>
<dd>An entity included with a response that is subject to content negotiation, as described in <a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 5</a> of <a href="#Part3" id="rfc.xref.Part3.14"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. There may exist multiple representations associated with a particular response status.
<p id="rfc.section.C.p.9"> <span id="rfc.iref.c.4"></span> <dfn>content negotiation</dfn>
<dd>The mechanism for selecting the appropriate representation when servicing a request, as described in <a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 5</a> of <a href="#Part3" id="rfc.xref.Part3.15"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. The representation of entities in any response can be negotiated (including error responses).
<p id="rfc.section.C.p.10"> <span id="rfc.iref.v.2"></span> <dfn>variant</dfn>
<dd>A resource may have one, or more than one, representation(s) associated with it at any given instant. Each of these representations
is termed a `variant'. Use of the term `variant' does not necessarily imply that the resource is subject to content negotiation.
<p id="rfc.section.C.p.11"> <span id="rfc.iref.c.5"></span> <dfn>client</dfn>
<p id="rfc.section.C.p.12"> <span id="rfc.iref.u.4"></span> <dfn>user agent</dfn>
<dd>The client which initiates a request. These are often browsers, editors, spiders (web-traversing robots), or other end user
<p id="rfc.section.C.p.13"> <span id="rfc.iref.s.1"></span> <dfn>server</dfn>
<dd>An application program that accepts connections in order to service requests by sending back responses. Any given program
may be capable of being both a client and a server; our use of these terms refers only to the role being performed by the
program for a particular connection, rather than to the program's capabilities in general. Likewise, any server may act as
an origin server, proxy, gateway, or tunnel, switching behavior based on the nature of each request.
<p id="rfc.section.C.p.14"> <span id="rfc.iref.o.1"></span> <dfn>origin server</dfn>
<p id="rfc.section.C.p.11"> <span id="rfc.iref.o.2"></span> <dfn>origin server</dfn>
<dd>The server on which a given resource resides or is to be created.</dd>
<p id="rfc.section.C.p.15"> <span id="rfc.iref.p.1"></span> <dfn>proxy</dfn>
<p id="rfc.section.C.p.12"> <span id="rfc.iref.p.1"></span> <dfn>proxy</dfn>
<p id="rfc.section.C.p.16"> <span id="rfc.iref.g.107"></span> <dfn>gateway</dfn>
<p id="rfc.section.C.p.13"> <span id="rfc.iref.r.1"></span> <dfn>request</dfn>
<p id="rfc.section.C.p.17"> <span id="rfc.iref.t.4"></span> <dfn>tunnel</dfn>
<p id="rfc.section.C.p.14"> <span id="rfc.iref.r.2"></span> <dfn>resource</dfn>
<p id="rfc.section.C.p.15"> <span id="rfc.iref.r.3"></span> <dfn>response</dfn>
<p id="rfc.section.C.p.16"> <span id="rfc.iref.r.4"></span> <dfn>representation</dfn>
<dd>An entity included with a response that is subject to content negotiation, as described in <a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 5</a> of <a href="#Part3" id="rfc.xref.Part3.15"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. There may exist multiple representations associated with a particular response status.
<p id="rfc.section.C.p.17"> <span id="rfc.iref.s.1"></span> <dfn>server</dfn>
<p id="rfc.section.C.p.18"> <span id="rfc.iref.t.4"></span> <dfn>tunnel</dfn>
<p id="rfc.section.C.p.18"> <span id="rfc.iref.c.6"></span> <dfn>cache</dfn>
<p id="rfc.section.C.p.19"> <span id="rfc.iref.c.7"></span> <dfn>cacheable</dfn>
<p id="rfc.section.C.p.20"> <span id="rfc.iref.u.5"></span> <span id="rfc.iref.d.2"></span> <dfn>upstream</dfn>/<dfn>downstream</dfn>
<p id="rfc.section.C.p.19"> <span id="rfc.iref.u.4"></span> <span id="rfc.iref.d.2"></span> <dfn>upstream</dfn>/<dfn>downstream</dfn>
<dd>Upstream and downstream describe the flow of a message: all messages flow from upstream to downstream.</dd>
<p id="rfc.section.C.p.21"> <span id="rfc.iref.i.1"></span> <span id="rfc.iref.o.2"></span> <dfn>inbound</dfn>/<dfn>outbound</dfn>
<p id="rfc.section.C.p.20"> <span id="rfc.iref.u.5"></span> <dfn>user agent</dfn>
<p id="rfc.section.C.p.21"> <span id="rfc.iref.v.2"></span> <dfn>variant</dfn>
<li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/52">http://tools.ietf.org/wg/httpbis/trac/ticket/52</a>&gt;: "Sort 1.3 Terminology"
<li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/63">http://tools.ietf.org/wg/httpbis/trac/ticket/63</a>&gt;: "RFC2047 encoded words"
<li class="indline1">cache&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.6">C</a></li>
<li class="indline1">cacheable&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.7">C</a></li>
<li class="indline1">cache&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.3">C</a></li>
<li class="indline1">cacheable&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.4">C</a></li>
<li class="indline1">client&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.5">C</a></li>
<li class="indline1">connection&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.3">C</a></li>
<li class="indline1">connection&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.6">C</a></li>
<li class="indline1">Connection header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.connection.1">4.5</a>, <a class="iref" href="#rfc.xref.header.connection.2">7.1.2</a>, <a class="iref" href="#rfc.xref.header.connection.3">7.1.3</a>, <a class="iref" href="#rfc.iref.c.1"><b>8.1</b></a>, <a class="iref" href="#rfc.xref.header.connection.4">8.5</a>, <a class="iref" href="#rfc.xref.header.connection.5">8.8</a>, <a class="iref" href="#rfc.xref.header.connection.6">9.1</a>, <a class="iref" href="#rfc.xref.header.connection.7">B.2</a>, <a class="iref" href="#rfc.xref.header.connection.8">B.4</a></li>
<li class="indline1">content negotiation&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.4">C</a></li>
<li class="indline1">content negotiation&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.7">C</a></li>
<li class="indline1">Content-Length header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-length.1">4.4</a>, <a class="iref" href="#rfc.iref.c.2"><b>8.2</b></a>, <a class="iref" href="#rfc.xref.header.content-length.2">9.1</a>, <a class="iref" href="#rfc.xref.header.content-length.3">B.3</a></li>
<li class="indline1">origin server&nbsp;&nbsp;<a class="iref" href="#rfc.iref.o.1">C</a></li>
<li class="indline1">outbound&nbsp;&nbsp;<a class="iref" href="#rfc.iref.o.2">C</a></li>
<li class="indline1">origin server&nbsp;&nbsp;<a class="iref" href="#rfc.iref.o.2">C</a></li>
<li class="indline1">outbound&nbsp;&nbsp;<a class="iref" href="#rfc.iref.o.1">C</a></li>
<li class="indline1"><em>Section 3.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.10">8.5</a></li>
<li class="indline1"><em>Section 4.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.5">1.2.3</a>, <a class="iref" href="#rfc.xref.Part3.8">5</a>, <a class="iref" href="#rfc.xref.Part3.9">6</a></li>
<li class="indline1"><em>Section 4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.13">C</a></li>
<li class="indline1"><em>Section 4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.14">C</a></li>
<li class="indline1"><em>Section 4.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.4">1.2.3</a></li>
<li class="indline1"><em>Section 5</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.14">C</a>, <a class="iref" href="#rfc.xref.Part3.15">C</a></li>
<li class="indline1"><em>Section 5</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.13">C</a>, <a class="iref" href="#rfc.xref.Part3.15">C</a></li>
<li class="indline1"><em>Section 6.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.3">1.2.3</a></li>
<li class="indline1"><em>Appendix A</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.1">1</a></li>
<li class="indline1">representation&nbsp;&nbsp;<a class="iref" href="#rfc.iref.r.4">C</a></li>
<li class="indline1">request&nbsp;&nbsp;<a class="iref" href="#rfc.iref.r.1">C</a></li>
<li class="indline1">resource&nbsp;&nbsp;<a class="iref" href="#rfc.iref.r.3">C</a></li>
<li class="indline1">response&nbsp;&nbsp;<a class="iref" href="#rfc.iref.r.2">C</a></li>
<li class="indline1">resource&nbsp;&nbsp;<a class="iref" href="#rfc.iref.r.2">C</a></li>
<li class="indline1">response&nbsp;&nbsp;<a class="iref" href="#rfc.iref.r.3">C</a></li>
<li class="indline1"><em>RFC1123</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1123.1">3.2.1</a>, <a class="iref" href="#RFC1123"><b>12.2</b></a></li>
<li class="indline1"><em>RFC1305</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1305.1">8.3</a>, <a class="iref" href="#RFC1305"><b>12.2</b></a></li>
<li class="indline1">Upgrade header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.upgrade.1">4.5</a>, <a class="iref" href="#rfc.iref.u.3"><b>8.8</b></a>, <a class="iref" href="#rfc.xref.header.upgrade.2">9.1</a></li>
<li class="indline1">upstream&nbsp;&nbsp;<a class="iref" href="#rfc.iref.u.5">C</a></li>
<li class="indline1">upstream&nbsp;&nbsp;<a class="iref" href="#rfc.iref.u.4">C</a></li>
<li class="indline1">URI scheme&nbsp;&nbsp;
<li class="indline1"><em>USASCII</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.USASCII.1">1.2</a>, <a class="iref" href="#rfc.xref.USASCII.2">4.2</a>, <a class="iref" href="#USASCII"><b>12.1</b></a></li>
<li class="indline1">user agent&nbsp;&nbsp;<a class="iref" href="#rfc.iref.u.4">C</a></li>
<li class="indline1">user agent&nbsp;&nbsp;<a class="iref" href="#rfc.iref.u.5">C</a></li>
<eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/52"/>:
"Sort 1.3 Terminology"
<eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/63"/>:
"RFC2047 encoded words"