Changeset 413
- Timestamp:
- 18/11/08 16:53:23 (14 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r404 r413 476 476 <tr> 477 477 <td class="header left"></td> 478 <td class="header right">November 1 5, 2008</td>478 <td class="header right">November 18, 2008</td> 479 479 </tr> 480 480 </table> … … 2487 2487 <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a> <a id="terminology" href="#terminology">Terminology</a></h1> 2488 2488 <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> 2489 <p id="rfc.section.C.p.2"> <span id="rfc.iref.c.3"></span> <dfn>connection</dfn> 2489 <p id="rfc.section.C.p.2"> <span id="rfc.iref.c.3"></span> <dfn>cache</dfn> 2490 </p> 2491 <dl class="empty"> 2492 <dd>A program's local store of response messages and the subsystem that controls its message storage, retrieval, and deletion. 2493 A cache stores cacheable responses in order to reduce the response time and network bandwidth consumption on future, equivalent 2494 requests. Any client or server may include a cache, though a cache cannot be used by a server that is acting as a tunnel. 2495 </dd> 2496 </dl> 2497 <p id="rfc.section.C.p.3"> <span id="rfc.iref.c.4"></span> <dfn>cacheable</dfn> 2498 </p> 2499 <dl class="empty"> 2500 <dd>A response is cacheable if a cache is allowed to store a copy of the response message for use in answering subsequent requests. 2501 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 2502 request. 2503 </dd> 2504 </dl> 2505 <p id="rfc.section.C.p.4"> <span id="rfc.iref.c.5"></span> <dfn>client</dfn> 2506 </p> 2507 <dl class="empty"> 2508 <dd>A program that establishes connections for the purpose of sending requests.</dd> 2509 </dl> 2510 <p id="rfc.section.C.p.5"> <span id="rfc.iref.c.6"></span> <dfn>connection</dfn> 2490 2511 </p> 2491 2512 <dl class="empty"> 2492 2513 <dd>A transport layer virtual circuit established between two programs for the purpose of communication.</dd> 2493 2514 </dl> 2494 <p id="rfc.section.C.p.3"> <span id="rfc.iref.m.4"></span> <dfn>message</dfn> 2515 <p id="rfc.section.C.p.6"> <span id="rfc.iref.c.7"></span> <dfn>content negotiation</dfn> 2516 </p> 2517 <dl class="empty"> 2518 <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). 2519 </dd> 2520 </dl> 2521 <p id="rfc.section.C.p.7"> <span id="rfc.iref.e.1"></span> <dfn>entity</dfn> 2522 </p> 2523 <dl class="empty"> 2524 <dd>The information transferred as the payload of a request or response. An entity consists of metainformation in the form of 2525 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>. 2526 </dd> 2527 </dl> 2528 <p id="rfc.section.C.p.8"> <span id="rfc.iref.g.107"></span> <dfn>gateway</dfn> 2529 </p> 2530 <dl class="empty"> 2531 <dd>A server which acts as an intermediary for some other server. Unlike a proxy, a gateway receives requests as if it were the 2532 origin server for the requested resource; the requesting client may not be aware that it is communicating with a gateway. 2533 </dd> 2534 </dl> 2535 <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> 2536 </p> 2537 <dl class="empty"> 2538 <dd>Inbound and outbound refer to the request and response paths for messages: "inbound" means "traveling toward the origin server", 2539 and "outbound" means "traveling toward the user agent" 2540 </dd> 2541 </dl> 2542 <p id="rfc.section.C.p.10"> <span id="rfc.iref.m.4"></span> <dfn>message</dfn> 2495 2543 </p> 2496 2544 <dl class="empty"> … … 2498 2546 </dd> 2499 2547 </dl> 2500 <p id="rfc.section.C.p.4"> <span id="rfc.iref.r.1"></span> <dfn>request</dfn> 2501 </p> 2502 <dl class="empty"> 2503 <dd>An HTTP request message, as defined in <a href="#request" title="Request">Section 5</a>. 2504 </dd> 2505 </dl> 2506 <p id="rfc.section.C.p.5"> <span id="rfc.iref.r.2"></span> <dfn>response</dfn> 2507 </p> 2508 <dl class="empty"> 2509 <dd>An HTTP response message, as defined in <a href="#response" title="Response">Section 6</a>. 2510 </dd> 2511 </dl> 2512 <p id="rfc.section.C.p.6"> <span id="rfc.iref.r.3"></span> <dfn>resource</dfn> 2513 </p> 2514 <dl class="empty"> 2515 <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 2.1</a>. Resources may be available in multiple representations (e.g. multiple languages, data formats, size, and resolutions) or 2516 vary in other ways. 2517 </dd> 2518 </dl> 2519 <p id="rfc.section.C.p.7"> <span id="rfc.iref.e.1"></span> <dfn>entity</dfn> 2520 </p> 2521 <dl class="empty"> 2522 <dd>The information transferred as the payload of a request or response. An entity consists of metainformation in the form of 2523 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>. 2524 </dd> 2525 </dl> 2526 <p id="rfc.section.C.p.8"> <span id="rfc.iref.r.4"></span> <dfn>representation</dfn> 2527 </p> 2528 <dl class="empty"> 2529 <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. 2530 </dd> 2531 </dl> 2532 <p id="rfc.section.C.p.9"> <span id="rfc.iref.c.4"></span> <dfn>content negotiation</dfn> 2533 </p> 2534 <dl class="empty"> 2535 <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). 2536 </dd> 2537 </dl> 2538 <p id="rfc.section.C.p.10"> <span id="rfc.iref.v.2"></span> <dfn>variant</dfn> 2539 </p> 2540 <dl class="empty"> 2541 <dd>A resource may have one, or more than one, representation(s) associated with it at any given instant. Each of these representations 2542 is termed a `variant'. Use of the term `variant' does not necessarily imply that the resource is subject to content negotiation. 2543 </dd> 2544 </dl> 2545 <p id="rfc.section.C.p.11"> <span id="rfc.iref.c.5"></span> <dfn>client</dfn> 2546 </p> 2547 <dl class="empty"> 2548 <dd>A program that establishes connections for the purpose of sending requests.</dd> 2549 </dl> 2550 <p id="rfc.section.C.p.12"> <span id="rfc.iref.u.4"></span> <dfn>user agent</dfn> 2551 </p> 2552 <dl class="empty"> 2553 <dd>The client which initiates a request. These are often browsers, editors, spiders (web-traversing robots), or other end user 2554 tools. 2555 </dd> 2556 </dl> 2557 <p id="rfc.section.C.p.13"> <span id="rfc.iref.s.1"></span> <dfn>server</dfn> 2558 </p> 2559 <dl class="empty"> 2560 <dd>An application program that accepts connections in order to service requests by sending back responses. Any given program 2561 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 2562 program for a particular connection, rather than to the program's capabilities in general. Likewise, any server may act as 2563 an origin server, proxy, gateway, or tunnel, switching behavior based on the nature of each request. 2564 </dd> 2565 </dl> 2566 <p id="rfc.section.C.p.14"> <span id="rfc.iref.o.1"></span> <dfn>origin server</dfn> 2548 <p id="rfc.section.C.p.11"> <span id="rfc.iref.o.2"></span> <dfn>origin server</dfn> 2567 2549 </p> 2568 2550 <dl class="empty"> 2569 2551 <dd>The server on which a given resource resides or is to be created.</dd> 2570 2552 </dl> 2571 <p id="rfc.section.C.p.1 5"> <span id="rfc.iref.p.1"></span> <dfn>proxy</dfn>2553 <p id="rfc.section.C.p.12"> <span id="rfc.iref.p.1"></span> <dfn>proxy</dfn> 2572 2554 </p> 2573 2555 <dl class="empty"> … … 2580 2562 </dd> 2581 2563 </dl> 2582 <p id="rfc.section.C.p.1 6"> <span id="rfc.iref.g.107"></span> <dfn>gateway</dfn>2564 <p id="rfc.section.C.p.13"> <span id="rfc.iref.r.1"></span> <dfn>request</dfn> 2583 2565 </p> 2584 2566 <dl class="empty"> 2585 <dd>A server which acts as an intermediary for some other server. Unlike a proxy, a gateway receives requests as if it were the 2586 origin server for the requested resource; the requesting client may not be aware that it is communicating with a gateway. 2567 <dd>An HTTP request message, as defined in <a href="#request" title="Request">Section 5</a>. 2587 2568 </dd> 2588 2569 </dl> 2589 <p id="rfc.section.C.p.17"> <span id="rfc.iref.t.4"></span> <dfn>tunnel</dfn> 2570 <p id="rfc.section.C.p.14"> <span id="rfc.iref.r.2"></span> <dfn>resource</dfn> 2571 </p> 2572 <dl class="empty"> 2573 <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 2.1</a>. Resources may be available in multiple representations (e.g. multiple languages, data formats, size, and resolutions) or 2574 vary in other ways. 2575 </dd> 2576 </dl> 2577 <p id="rfc.section.C.p.15"> <span id="rfc.iref.r.3"></span> <dfn>response</dfn> 2578 </p> 2579 <dl class="empty"> 2580 <dd>An HTTP response message, as defined in <a href="#response" title="Response">Section 6</a>. 2581 </dd> 2582 </dl> 2583 <p id="rfc.section.C.p.16"> <span id="rfc.iref.r.4"></span> <dfn>representation</dfn> 2584 </p> 2585 <dl class="empty"> 2586 <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. 2587 </dd> 2588 </dl> 2589 <p id="rfc.section.C.p.17"> <span id="rfc.iref.s.1"></span> <dfn>server</dfn> 2590 </p> 2591 <dl class="empty"> 2592 <dd>An application program that accepts connections in order to service requests by sending back responses. Any given program 2593 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 2594 program for a particular connection, rather than to the program's capabilities in general. Likewise, any server may act as 2595 an origin server, proxy, gateway, or tunnel, switching behavior based on the nature of each request. 2596 </dd> 2597 </dl> 2598 <p id="rfc.section.C.p.18"> <span id="rfc.iref.t.4"></span> <dfn>tunnel</dfn> 2590 2599 </p> 2591 2600 <dl class="empty"> … … 2595 2604 </dd> 2596 2605 </dl> 2597 <p id="rfc.section.C.p.18"> <span id="rfc.iref.c.6"></span> <dfn>cache</dfn> 2598 </p> 2599 <dl class="empty"> 2600 <dd>A program's local store of response messages and the subsystem that controls its message storage, retrieval, and deletion. 2601 A cache stores cacheable responses in order to reduce the response time and network bandwidth consumption on future, equivalent 2602 requests. Any client or server may include a cache, though a cache cannot be used by a server that is acting as a tunnel. 2603 </dd> 2604 </dl> 2605 <p id="rfc.section.C.p.19"> <span id="rfc.iref.c.7"></span> <dfn>cacheable</dfn> 2606 </p> 2607 <dl class="empty"> 2608 <dd>A response is cacheable if a cache is allowed to store a copy of the response message for use in answering subsequent requests. 2609 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 2610 request. 2611 </dd> 2612 </dl> 2613 <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> 2606 <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> 2614 2607 </p> 2615 2608 <dl class="empty"> 2616 2609 <dd>Upstream and downstream describe the flow of a message: all messages flow from upstream to downstream.</dd> 2617 2610 </dl> 2618 <p id="rfc.section.C.p.2 1"> <span id="rfc.iref.i.1"></span> <span id="rfc.iref.o.2"></span> <dfn>inbound</dfn>/<dfn>outbound</dfn>2611 <p id="rfc.section.C.p.20"> <span id="rfc.iref.u.5"></span> <dfn>user agent</dfn> 2619 2612 </p> 2620 2613 <dl class="empty"> 2621 <dd>Inbound and outbound refer to the request and response paths for messages: "inbound" means "traveling toward the origin server", 2622 and "outbound" means "traveling toward the user agent" 2614 <dd>The client which initiates a request. These are often browsers, editors, spiders (web-traversing robots), or other end user 2615 tools. 2616 </dd> 2617 </dl> 2618 <p id="rfc.section.C.p.21"> <span id="rfc.iref.v.2"></span> <dfn>variant</dfn> 2619 </p> 2620 <dl class="empty"> 2621 <dd>A resource may have one, or more than one, representation(s) associated with it at any given instant. Each of these representations 2622 is termed a `variant'. Use of the term `variant' does not necessarily imply that the resource is subject to content negotiation. 2623 2623 </dd> 2624 2624 </dl> … … 2767 2767 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/30">http://tools.ietf.org/wg/httpbis/trac/ticket/30</a>>: "Header LWS" 2768 2768 </li> 2769 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/52">http://tools.ietf.org/wg/httpbis/trac/ticket/52</a>>: "Sort 1.3 Terminology" 2770 </li> 2769 2771 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/63">http://tools.ietf.org/wg/httpbis/trac/ticket/63</a>>: "RFC2047 encoded words" 2770 2772 </li> … … 2827 2829 </li> 2828 2830 <li class="indline0"><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul class="ind"> 2829 <li class="indline1">cache <a class="iref" href="#rfc.iref.c. 6">C</a></li>2830 <li class="indline1">cacheable <a class="iref" href="#rfc.iref.c. 7">C</a></li>2831 <li class="indline1">cache <a class="iref" href="#rfc.iref.c.3">C</a></li> 2832 <li class="indline1">cacheable <a class="iref" href="#rfc.iref.c.4">C</a></li> 2831 2833 <li class="indline1">client <a class="iref" href="#rfc.iref.c.5">C</a></li> 2832 <li class="indline1">connection <a class="iref" href="#rfc.iref.c. 3">C</a></li>2834 <li class="indline1">connection <a class="iref" href="#rfc.iref.c.6">C</a></li> 2833 2835 <li class="indline1">Connection header <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> 2834 <li class="indline1">content negotiation <a class="iref" href="#rfc.iref.c. 4">C</a></li>2836 <li class="indline1">content negotiation <a class="iref" href="#rfc.iref.c.7">C</a></li> 2835 2837 <li class="indline1">Content-Length header <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> 2836 2838 </ul> … … 3003 3005 </li> 3004 3006 <li class="indline0"><a id="rfc.index.O" href="#rfc.index.O"><b>O</b></a><ul class="ind"> 3005 <li class="indline1">origin server <a class="iref" href="#rfc.iref.o. 1">C</a></li>3006 <li class="indline1">outbound <a class="iref" href="#rfc.iref.o. 2">C</a></li>3007 <li class="indline1">origin server <a class="iref" href="#rfc.iref.o.2">C</a></li> 3008 <li class="indline1">outbound <a class="iref" href="#rfc.iref.o.1">C</a></li> 3007 3009 </ul> 3008 3010 </li> … … 3027 3029 <li class="indline1"><em>Section 3.4</em> <a class="iref" href="#rfc.xref.Part3.10">8.5</a></li> 3028 3030 <li class="indline1"><em>Section 4.1</em> <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> 3029 <li class="indline1"><em>Section 4</em> <a class="iref" href="#rfc.xref.Part3.1 3">C</a></li>3031 <li class="indline1"><em>Section 4</em> <a class="iref" href="#rfc.xref.Part3.14">C</a></li> 3030 3032 <li class="indline1"><em>Section 4.2</em> <a class="iref" href="#rfc.xref.Part3.4">1.2.3</a></li> 3031 <li class="indline1"><em>Section 5</em> <a class="iref" href="#rfc.xref.Part3.1 4">C</a>, <a class="iref" href="#rfc.xref.Part3.15">C</a></li>3033 <li class="indline1"><em>Section 5</em> <a class="iref" href="#rfc.xref.Part3.13">C</a>, <a class="iref" href="#rfc.xref.Part3.15">C</a></li> 3032 3034 <li class="indline1"><em>Section 6.1</em> <a class="iref" href="#rfc.xref.Part3.3">1.2.3</a></li> 3033 3035 <li class="indline1"><em>Appendix A</em> <a class="iref" href="#rfc.xref.Part3.1">1</a></li> … … 3048 3050 <li class="indline1">representation <a class="iref" href="#rfc.iref.r.4">C</a></li> 3049 3051 <li class="indline1">request <a class="iref" href="#rfc.iref.r.1">C</a></li> 3050 <li class="indline1">resource <a class="iref" href="#rfc.iref.r. 3">C</a></li>3051 <li class="indline1">response <a class="iref" href="#rfc.iref.r. 2">C</a></li>3052 <li class="indline1">resource <a class="iref" href="#rfc.iref.r.2">C</a></li> 3053 <li class="indline1">response <a class="iref" href="#rfc.iref.r.3">C</a></li> 3052 3054 <li class="indline1"><em>RFC1123</em> <a class="iref" href="#rfc.xref.RFC1123.1">3.2.1</a>, <a class="iref" href="#RFC1123"><b>12.2</b></a></li> 3053 3055 <li class="indline1"><em>RFC1305</em> <a class="iref" href="#rfc.xref.RFC1305.1">8.3</a>, <a class="iref" href="#RFC1305"><b>12.2</b></a></li> … … 3114 3116 <li class="indline0"><a id="rfc.index.U" href="#rfc.index.U"><b>U</b></a><ul class="ind"> 3115 3117 <li class="indline1">Upgrade header <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> 3116 <li class="indline1">upstream <a class="iref" href="#rfc.iref.u. 5">C</a></li>3118 <li class="indline1">upstream <a class="iref" href="#rfc.iref.u.4">C</a></li> 3117 3119 <li class="indline1">URI scheme 3118 3120 <ul class="ind"> … … 3122 3124 </li> 3123 3125 <li class="indline1"><em>USASCII</em> <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> 3124 <li class="indline1">user agent <a class="iref" href="#rfc.iref.u. 4">C</a></li>3126 <li class="indline1">user agent <a class="iref" href="#rfc.iref.u.5">C</a></li> 3125 3127 </ul> 3126 3128 </li> -
draft-ietf-httpbis/latest/p1-messaging.xml
r404 r413 4157 4157 </t> 4158 4158 <t> 4159 <iref item="cache"/> 4160 <x:dfn>cache</x:dfn> 4161 <list> 4162 <t> 4163 A program's local store of response messages and the subsystem 4164 that controls its message storage, retrieval, and deletion. A 4165 cache stores cacheable responses in order to reduce the response 4166 time and network bandwidth consumption on future, equivalent 4167 requests. Any client or server may include a cache, though a cache 4168 cannot be used by a server that is acting as a tunnel. 4169 </t> 4170 </list> 4171 </t> 4172 <t> 4173 <iref item="cacheable"/> 4174 <x:dfn>cacheable</x:dfn> 4175 <list> 4176 <t> 4177 A response is cacheable if a cache is allowed to store a copy of 4178 the response message for use in answering subsequent requests. The 4179 rules for determining the cacheability of HTTP responses are 4180 defined in &caching;. Even if a resource is cacheable, there may 4181 be additional constraints on whether a cache can use the cached 4182 copy for a particular request. 4183 </t> 4184 </list> 4185 </t> 4186 <t> 4187 <iref item="client"/> 4188 <x:dfn>client</x:dfn> 4189 <list> 4190 <t> 4191 A program that establishes connections for the purpose of sending 4192 requests. 4193 </t> 4194 </list> 4195 </t> 4196 <t> 4159 4197 <iref item="connection"/> 4160 4198 <x:dfn>connection</x:dfn> … … 4167 4205 </t> 4168 4206 <t> 4169 <iref item=" message"/>4170 <x:dfn> message</x:dfn>4207 <iref item="content negotiation"/> 4208 <x:dfn>content negotiation</x:dfn> 4171 4209 <list> 4172 4210 <t> 4173 The basic unit of HTTP communication, consisting of a structured 4174 sequence of octets matching the syntax defined in <xref target="http.message"/> and 4175 transmitted via the connection. 4176 </t> 4177 </list> 4178 </t> 4179 <t> 4180 <iref item="request"/> 4181 <x:dfn>request</x:dfn> 4182 <list> 4183 <t> 4184 An HTTP request message, as defined in <xref target="request"/>. 4185 </t> 4186 </list> 4187 </t> 4188 <t> 4189 <iref item="response"/> 4190 <x:dfn>response</x:dfn> 4191 <list> 4192 <t> 4193 An HTTP response message, as defined in <xref target="response"/>. 4194 </t> 4195 </list> 4196 </t> 4197 <t> 4198 <iref item="resource"/> 4199 <x:dfn>resource</x:dfn> 4200 <list> 4201 <t> 4202 A network data object or service that can be identified by a URI, 4203 as defined in <xref target="uri"/>. Resources may be available in multiple 4204 representations (e.g. multiple languages, data formats, size, and 4205 resolutions) or vary in other ways. 4211 The mechanism for selecting the appropriate representation when 4212 servicing a request, as described in &content.negotiation;. The 4213 representation of entities in any response can be negotiated 4214 (including error responses). 4206 4215 </t> 4207 4216 </list> … … 4220 4229 </t> 4221 4230 <t> 4222 <iref item=" representation"/>4223 <x:dfn> representation</x:dfn>4231 <iref item="gateway"/> 4232 <x:dfn>gateway</x:dfn> 4224 4233 <list> 4225 4234 <t> 4226 An entity included with a response that is subject to content 4227 negotiation, as described in &content.negotiation;. There may exist multiple 4228 representations associated with a particular response status. 4229 </t> 4230 </list> 4231 </t> 4232 <t> 4233 <iref item="content negotiation"/> 4234 <x:dfn>content negotiation</x:dfn> 4235 A server which acts as an intermediary for some other server. 4236 Unlike a proxy, a gateway receives requests as if it were the 4237 origin server for the requested resource; the requesting client 4238 may not be aware that it is communicating with a gateway. 4239 </t> 4240 </list> 4241 </t> 4242 <t> 4243 <iref item="inbound"/> 4244 <iref item="outbound"/> 4245 <x:dfn>inbound</x:dfn>/<x:dfn>outbound</x:dfn> 4235 4246 <list> 4236 4247 <t> 4237 The mechanism for selecting the appropriate representation when 4238 servicing a request, as described in &content.negotiation;. The 4239 representation of entities in any response can be negotiated 4240 (including error responses). 4241 </t> 4242 </list> 4243 </t> 4244 <t> 4245 <iref item="variant"/> 4246 <x:dfn>variant</x:dfn> 4248 Inbound and outbound refer to the request and response paths for 4249 messages: "inbound" means "traveling toward the origin server", 4250 and "outbound" means "traveling toward the user agent" 4251 </t> 4252 </list> 4253 </t> 4254 <t> 4255 <iref item="message"/> 4256 <x:dfn>message</x:dfn> 4247 4257 <list> 4248 4258 <t> 4249 A resource may have one, or more than one, representation(s) 4250 associated with it at any given instant. Each of these 4251 representations is termed a `variant'. Use of the term `variant' 4252 does not necessarily imply that the resource is subject to content 4253 negotiation. 4254 </t> 4255 </list> 4256 </t> 4257 <t> 4258 <iref item="client"/> 4259 <x:dfn>client</x:dfn> 4260 <list> 4261 <t> 4262 A program that establishes connections for the purpose of sending 4263 requests. 4264 </t> 4265 </list> 4266 </t> 4267 <t> 4268 <iref item="user agent"/> 4269 <x:dfn>user agent</x:dfn> 4270 <list> 4271 <t> 4272 The client which initiates a request. These are often browsers, 4273 editors, spiders (web-traversing robots), or other end user tools. 4274 </t> 4275 </list> 4276 </t> 4277 <t> 4278 <iref item="server"/> 4279 <x:dfn>server</x:dfn> 4280 <list> 4281 <t> 4282 An application program that accepts connections in order to 4283 service requests by sending back responses. Any given program may 4284 be capable of being both a client and a server; our use of these 4285 terms refers only to the role being performed by the program for a 4286 particular connection, rather than to the program's capabilities 4287 in general. Likewise, any server may act as an origin server, 4288 proxy, gateway, or tunnel, switching behavior based on the nature 4289 of each request. 4259 The basic unit of HTTP communication, consisting of a structured 4260 sequence of octets matching the syntax defined in <xref target="http.message"/> and 4261 transmitted via the connection. 4290 4262 </t> 4291 4263 </list> … … 4323 4295 </t> 4324 4296 <t> 4325 <iref item=" gateway"/>4326 <x:dfn> gateway</x:dfn>4297 <iref item="request"/> 4298 <x:dfn>request</x:dfn> 4327 4299 <list> 4328 4300 <t> 4329 A server which acts as an intermediary for some other server. 4330 Unlike a proxy, a gateway receives requests as if it were the 4331 origin server for the requested resource; the requesting client 4332 may not be aware that it is communicating with a gateway. 4301 An HTTP request message, as defined in <xref target="request"/>. 4302 </t> 4303 </list> 4304 </t> 4305 <t> 4306 <iref item="resource"/> 4307 <x:dfn>resource</x:dfn> 4308 <list> 4309 <t> 4310 A network data object or service that can be identified by a URI, 4311 as defined in <xref target="uri"/>. Resources may be available in multiple 4312 representations (e.g. multiple languages, data formats, size, and 4313 resolutions) or vary in other ways. 4314 </t> 4315 </list> 4316 </t> 4317 <t> 4318 <iref item="response"/> 4319 <x:dfn>response</x:dfn> 4320 <list> 4321 <t> 4322 An HTTP response message, as defined in <xref target="response"/>. 4323 </t> 4324 </list> 4325 </t> 4326 <t> 4327 <iref item="representation"/> 4328 <x:dfn>representation</x:dfn> 4329 <list> 4330 <t> 4331 An entity included with a response that is subject to content 4332 negotiation, as described in &content.negotiation;. There may exist multiple 4333 representations associated with a particular response status. 4334 </t> 4335 </list> 4336 </t> 4337 <t> 4338 <iref item="server"/> 4339 <x:dfn>server</x:dfn> 4340 <list> 4341 <t> 4342 An application program that accepts connections in order to 4343 service requests by sending back responses. Any given program may 4344 be capable of being both a client and a server; our use of these 4345 terms refers only to the role being performed by the program for a 4346 particular connection, rather than to the program's capabilities 4347 in general. Likewise, any server may act as an origin server, 4348 proxy, gateway, or tunnel, switching behavior based on the nature 4349 of each request. 4333 4350 </t> 4334 4351 </list> … … 4348 4365 </t> 4349 4366 <t> 4350 <iref item="cache"/>4351 <x:dfn>cache</x:dfn>4352 <list>4353 <t>4354 A program's local store of response messages and the subsystem4355 that controls its message storage, retrieval, and deletion. A4356 cache stores cacheable responses in order to reduce the response4357 time and network bandwidth consumption on future, equivalent4358 requests. Any client or server may include a cache, though a cache4359 cannot be used by a server that is acting as a tunnel.4360 </t>4361 </list>4362 </t>4363 <t>4364 <iref item="cacheable"/>4365 <x:dfn>cacheable</x:dfn>4366 <list>4367 <t>4368 A response is cacheable if a cache is allowed to store a copy of4369 the response message for use in answering subsequent requests. The4370 rules for determining the cacheability of HTTP responses are4371 defined in &caching;. Even if a resource is cacheable, there may4372 be additional constraints on whether a cache can use the cached4373 copy for a particular request.4374 </t>4375 </list>4376 </t>4377 <t>4378 4367 <iref item="upstream"/> 4379 4368 <iref item="downstream"/> … … 4387 4376 </t> 4388 4377 <t> 4389 <iref item="inbound"/> 4390 <iref item="outbound"/> 4391 <x:dfn>inbound</x:dfn>/<x:dfn>outbound</x:dfn> 4378 <iref item="user agent"/> 4379 <x:dfn>user agent</x:dfn> 4392 4380 <list> 4393 4381 <t> 4394 Inbound and outbound refer to the request and response paths for 4395 messages: "inbound" means "traveling toward the origin server", 4396 and "outbound" means "traveling toward the user agent" 4382 The client which initiates a request. These are often browsers, 4383 editors, spiders (web-traversing robots), or other end user tools. 4384 </t> 4385 </list> 4386 </t> 4387 <t> 4388 <iref item="variant"/> 4389 <x:dfn>variant</x:dfn> 4390 <list> 4391 <t> 4392 A resource may have one, or more than one, representation(s) 4393 associated with it at any given instant. Each of these 4394 representations is termed a `variant'. Use of the term `variant' 4395 does not necessarily imply that the resource is subject to content 4396 negotiation. 4397 4397 </t> 4398 4398 </list> … … 4697 4697 </t> 4698 4698 <t> 4699 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/52"/>: 4700 "Sort 1.3 Terminology" 4701 </t> 4702 <t> 4699 4703 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/63"/>: 4700 4704 "RFC2047 encoded words"
Note: See TracChangeset
for help on using the changeset viewer.