* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Changeset 1488


Ignore:
Timestamp:
2011-12-05 14:51:33 (3 years ago)
Author:
julian.reschke@gmx.de
Message:

clarify user agent (see #166)

Location:
draft-ietf-httpbis/latest
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.html

    r1481 r1488  
    359359  }  
    360360  @bottom-center { 
    361        content: "Expires June 3, 2012";  
     361       content: "Expires June 7, 2012";  
    362362  }  
    363363  @bottom-right { 
     
    409409      <meta name="dct.creator" content="Reschke, J. F."> 
    410410      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 
    411       <meta name="dct.issued" scheme="ISO8601" content="2011-12-01"> 
     411      <meta name="dct.issued" scheme="ISO8601" content="2011-12-05"> 
    412412      <meta name="dct.replaces" content="urn:ietf:rfc:2145"> 
    413413      <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 
     
    441441            </tr> 
    442442            <tr> 
    443                <td class="left">Expires: June 3, 2012</td> 
     443               <td class="left">Expires: June 7, 2012</td> 
    444444               <td class="right">HP</td> 
    445445            </tr> 
     
    494494            <tr> 
    495495               <td class="left"></td> 
    496                <td class="right">December 1, 2011</td> 
     496               <td class="right">December 5, 2011</td> 
    497497            </tr> 
    498498         </tbody> 
     
    527527         in progress”. 
    528528      </p> 
    529       <p>This Internet-Draft will expire on June 3, 2012.</p> 
     529      <p>This Internet-Draft will expire on June 7, 2012.</p> 
    530530      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 
    531531      <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> 
     
    879879         "<dfn>sender</dfn>" to refer to whichever component sent a given message and the term "<dfn>recipient</dfn>" to refer to any component that receives the message. 
    880880      </p> 
    881       <p id="rfc.section.2.1.p.3">Most HTTP communication consists of a retrieval request (GET) for a representation of some resource identified by a URI. In 
     881      <div class="note" id="rfc.section.2.1.p.3">  
     882         <p> <b>Note:</b> The term 'user agent' covers both those situations where there is a user (human) interacting with the software agent (and 
     883            for which user interface or interactive suggestions might be made, e.g., warning the user or given the user an option in the 
     884            case of security or privacy options) and also those where the software agent may act autonomously. 
     885         </p>  
     886      </div> 
     887      <p id="rfc.section.2.1.p.4">Most HTTP communication consists of a retrieval request (GET) for a representation of some resource identified by a URI. In 
    882888         the simplest case, this might be accomplished via a single bidirectional connection (===) between the user agent (UA) and 
    883889         the origin server (O). 
     
    889895      <div id="rfc.iref.r.2"></div> 
    890896      <div id="rfc.iref.r.3"></div> 
    891       <p id="rfc.section.2.1.p.5">A client sends an HTTP request to the server in the form of a <dfn>request</dfn> message, beginning with a request-line that includes a method, URI, and protocol version (<a href="#request.line" title="Request-Line">Section&nbsp;3.1.1</a>), followed by MIME-like header fields containing request modifiers, client information, and payload metadata (<a href="#header.fields" title="Header Fields">Section&nbsp;3.2</a>), an empty line to indicate the end of the header section, and finally a message body containing the payload body (if any, <a href="#message.body" title="Message Body">Section&nbsp;3.3</a>). 
    892       </p> 
    893       <p id="rfc.section.2.1.p.6">A server responds to the client's request by sending an HTTP <dfn>response</dfn> message, beginning with a status line that includes the protocol version, a success or error code, and textual reason phrase 
     897      <p id="rfc.section.2.1.p.6">A client sends an HTTP request to the server in the form of a <dfn>request</dfn> message, beginning with a request-line that includes a method, URI, and protocol version (<a href="#request.line" title="Request-Line">Section&nbsp;3.1.1</a>), followed by MIME-like header fields containing request modifiers, client information, and payload metadata (<a href="#header.fields" title="Header Fields">Section&nbsp;3.2</a>), an empty line to indicate the end of the header section, and finally a message body containing the payload body (if any, <a href="#message.body" title="Message Body">Section&nbsp;3.3</a>). 
     898      </p> 
     899      <p id="rfc.section.2.1.p.7">A server responds to the client's request by sending an HTTP <dfn>response</dfn> message, beginning with a status line that includes the protocol version, a success or error code, and textual reason phrase 
    894900         (<a href="#status.line" title="Response Status-Line">Section&nbsp;3.1.2</a>), followed by MIME-like header fields containing server information, resource metadata, and payload metadata (<a href="#header.fields" title="Header Fields">Section&nbsp;3.2</a>), an empty line to indicate the end of the header section, and finally a message body containing the payload body (if any, <a href="#message.body" title="Message Body">Section&nbsp;3.3</a>). 
    895901      </p> 
    896       <p id="rfc.section.2.1.p.7">Note that 1xx responses (<a href="p2-semantics.html#status.1xx" title="Informational 1xx">Section 7.1</a> of <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) are not final; therefore, a server can send zero or more 1xx responses, followed by exactly one final response (with any 
     902      <p id="rfc.section.2.1.p.8">Note that 1xx responses (<a href="p2-semantics.html#status.1xx" title="Informational 1xx">Section 7.1</a> of <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) are not final; therefore, a server can send zero or more 1xx responses, followed by exactly one final response (with any 
    897903         other status code). 
    898904      </p> 
    899       <p id="rfc.section.2.1.p.8">The following example illustrates a typical message exchange for a GET request on the URI "http://www.example.com/hello.txt":</p> 
     905      <p id="rfc.section.2.1.p.9">The following example illustrates a typical message exchange for a GET request on the URI "http://www.example.com/hello.txt":</p> 
    900906      <div id="rfc.figure.u.10"></div> 
    901907      <p>client request:</p><pre class="text2">GET /hello.txt HTTP/1.1 
     
    34793485      <p id="rfc.section.C.19.p.1">Closed issues: </p> 
    34803486      <ul> 
     3487         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/166">http://tools.ietf.org/wg/httpbis/trac/ticket/166</a>&gt;: "Clarify 'User Agent'" 
     3488         </li> 
    34813489         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/300">http://tools.ietf.org/wg/httpbis/trac/ticket/300</a>&gt;: "Define non-final responses" 
    34823490         </li> 
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r1481 r1488  
    536536   message. 
    537537</t> 
     538<x:note> 
     539  <t> 
     540    <x:h>Note:</x:h> The term 'user agent' covers both those situations where 
     541    there is a user (human) interacting with the software agent (and for which 
     542    user interface or interactive suggestions might be made, e.g., warning the 
     543    user or given the user an option in the case of security or privacy 
     544    options) and also those where the software agent may act autonomously. 
     545  </t> 
     546</x:note> 
    538547<t> 
    539548   Most HTTP communication consists of a retrieval request (GET) for 
     
    58665875  <list style="symbols"> 
    58675876    <t> 
     5877      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/166"/>: 
     5878      "Clarify 'User Agent'" 
     5879    </t> 
     5880    <t> 
    58685881      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/300"/>: 
    58695882      "Define non-final responses" 
Note: See TracChangeset for help on using the changeset viewer.