Changeset 1957


Ignore:
Timestamp:
30/10/12 13:39:53 (10 years ago)
Author:
julian.reschke@…
Message:

"user-agent" -> "user agent" (see #234)

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

Legend:

Unmodified
Added
Removed

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

    r1943 r1957  
    449449  }
    450450  @bottom-center {
    451        content: "Expires April 25, 2013";
     451       content: "Expires May 3, 2013";
    452452  }
    453453  @bottom-right {
    … …  
    491491      <meta name="dct.creator" content="Reschke, J. F.">
    492492      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest">
    493       <meta name="dct.issued" scheme="ISO8601" content="2012-10-22">
     493      <meta name="dct.issued" scheme="ISO8601" content="2012-10-30">
    494494      <meta name="dct.replaces" content="urn:ietf:rfc:2145">
    495495      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    … …  
    520520            <tr>
    521521               <td class="left">Intended status: Standards Track</td>
    522                <td class="right">October 22, 2012</td>
     522               <td class="right">October 30, 2012</td>
    523523            </tr>
    524524            <tr>
    525                <td class="left">Expires: April 25, 2013</td>
     525               <td class="left">Expires: May 3, 2013</td>
    526526               <td class="right"></td>
    527527            </tr>
    … …  
    551551         in progress”.
    552552      </p>
    553       <p>This Internet-Draft will expire on April 25, 2013.</p>
     553      <p>This Internet-Draft will expire on May 3, 2013.</p>
    554554      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    555555      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    … …  
    14311431         <li>
    14321432            <p>If a message is received without <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding</a> and with either multiple <a href="#header.content-length" class="smpl">Content-Length</a> header fields having differing field-values or a single Content-Length header field having an invalid value, then the message
    1433                framing is invalid and <em class="bcp14">MUST</em> be treated as an error to prevent request or response smuggling. If this is a request message, the server <em class="bcp14">MUST</em> respond with a <a href="p2-semantics.html#status.400" class="smpl">400 (Bad Request)</a> status code and then close the connection. If this is a response message received by a proxy, the proxy <em class="bcp14">MUST</em> discard the received response, send a <a href="p2-semantics.html#status.502" class="smpl">502 (Bad Gateway)</a> status code as its downstream response, and then close the connection. If this is a response message received by a user-agent,
     1433               framing is invalid and <em class="bcp14">MUST</em> be treated as an error to prevent request or response smuggling. If this is a request message, the server <em class="bcp14">MUST</em> respond with a <a href="p2-semantics.html#status.400" class="smpl">400 (Bad Request)</a> status code and then close the connection. If this is a response message received by a proxy, the proxy <em class="bcp14">MUST</em> discard the received response, send a <a href="p2-semantics.html#status.502" class="smpl">502 (Bad Gateway)</a> status code as its downstream response, and then close the connection. If this is a response message received by a user agent,
    14341434               it <em class="bcp14">MUST</em> be treated as an error by discarding the message and closing the connection.
    14351435            </p>
    … …  
    14381438            <p>If a valid <a href="#header.content-length" class="smpl">Content-Length</a> header field is present without <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding</a>, its decimal value defines the message body length in octets. If the actual number of octets sent in the message is less
    14391439               than the indicated Content-Length, the recipient <em class="bcp14">MUST</em> consider the message to be incomplete and treat the connection as no longer usable. If the actual number of octets sent in
    1440                the message is more than the indicated Content-Length, the recipient <em class="bcp14">MUST</em> only process the message body up to the field value's number of octets; the remainder of the message <em class="bcp14">MUST</em> either be discarded or treated as the next message in a pipeline. For the sake of robustness, a user-agent <em class="bcp14">MAY</em> attempt to detect and correct such an error in message framing if it is parsing the response to the last request on a connection
     1440               the message is more than the indicated Content-Length, the recipient <em class="bcp14">MUST</em> only process the message body up to the field value's number of octets; the remainder of the message <em class="bcp14">MUST</em> either be discarded or treated as the next message in a pipeline. For the sake of robustness, a user agent <em class="bcp14">MAY</em> attempt to detect and correct such an error in message framing if it is parsing the response to the last request on a connection
    14411441               and the connection has been closed by the server.
    14421442            </p>
    … …  
    20262026      <h4 id="rfc.section.6.2.2.2"><a href="#rfc.section.6.2.2.2">6.2.2.2</a>&nbsp;<a id="persistent.retrying.requests" href="#persistent.retrying.requests">Retrying Requests</a></h4>
    20272027      <p id="rfc.section.6.2.2.2.p.1">Senders can close the transport connection at any time. Therefore, clients, servers, and proxies <em class="bcp14">MUST</em> be able to recover from asynchronous close events. Client software <em class="bcp14">MAY</em> reopen the transport connection and retransmit the aborted sequence of requests without user interaction so long as the request
    2028          sequence is idempotent (see <a href="p2-semantics.html#idempotent.methods" title="Idempotent Methods">Section 5.2.2</a> of <a href="#Part2" id="rfc.xref.Part2.28"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>). Non-idempotent request methods or sequences <em class="bcp14">MUST NOT</em> be automatically retried, although user agents <em class="bcp14">MAY</em> offer a human operator the choice of retrying the request(s). Confirmation by user-agent software with semantic understanding
     2028         sequence is idempotent (see <a href="p2-semantics.html#idempotent.methods" title="Idempotent Methods">Section 5.2.2</a> of <a href="#Part2" id="rfc.xref.Part2.28"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>). Non-idempotent request methods or sequences <em class="bcp14">MUST NOT</em> be automatically retried, although user agents <em class="bcp14">MAY</em> offer a human operator the choice of retrying the request(s). Confirmation by user agent software with semantic understanding
    20292029         of the application <em class="bcp14">MAY</em> substitute for user confirmation. The automatic retry <em class="bcp14">SHOULD NOT</em> be repeated if the second sequence of requests fails.
    20302030      </p>

  • draft-ietf-httpbis/latest/p1-messaging.xml

    r1943 r1957  
    16771677     &MUST; discard the received response, send a <x:ref>502 (Bad Gateway)</x:ref>
    16781678     status code as its downstream response, and then close the connection.
    1679      If this is a response message received by a user-agent, it &MUST; be
     1679     If this is a response message received by a user agent, it &MUST; be
    16801680     treated as an error by discarding the message and closing the connection.
    16811681    </t></x:lt>
    … …  
    16911691     field value's number of octets; the remainder of the message &MUST; either
    16921692     be discarded or treated as the next message in a pipeline.  For the sake of
    1693      robustness, a user-agent &MAY; attempt to detect and correct such an error
     1693     robustness, a user agent &MAY; attempt to detect and correct such an error
    16941694     in message framing if it is parsing the response to the last request on
    16951695     a connection and the connection has been closed by the server.
    … …  
    29082908   &MUST-NOT; be automatically retried, although user agents &MAY; offer a
    29092909   human operator the choice of retrying the request(s). Confirmation by
    2910    user-agent software with semantic understanding of the application
     2910   user agent software with semantic understanding of the application
    29112911   &MAY; substitute for user confirmation. The automatic retry &SHOULD-NOT;
    29122912   be repeated if the second sequence of requests fails.

  • draft-ietf-httpbis/latest/p2-semantics.html

    r1950 r1957  
    449449  }
    450450  @bottom-center {
    451        content: "Expires April 27, 2013";
     451       content: "Expires May 3, 2013";
    452452  }
    453453  @bottom-right {
    … …  
    496496      <meta name="dct.creator" content="Reschke, J. F.">
    497497      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
    498       <meta name="dct.issued" scheme="ISO8601" content="2012-10-24">
     498      <meta name="dct.issued" scheme="ISO8601" content="2012-10-30">
    499499      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    500500      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation.">
    … …  
    524524            <tr>
    525525               <td class="left">Intended status: Standards Track</td>
    526                <td class="right">October 24, 2012</td>
     526               <td class="right">October 30, 2012</td>
    527527            </tr>
    528528            <tr>
    529                <td class="left">Expires: April 27, 2013</td>
     529               <td class="left">Expires: May 3, 2013</td>
    530530               <td class="right"></td>
    531531            </tr>
    … …  
    555555         in progress”.
    556556      </p>
    557       <p>This Internet-Draft will expire on April 27, 2013.</p>
     557      <p>This Internet-Draft will expire on May 3, 2013.</p>
    558558      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    559559      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    … …  
    12111211      <p id="rfc.section.3.4.p.4">These patterns are all widely used, and have trade-offs in applicability and practicality. In particular, when the number
    12121212         of preferences or capabilities to be expressed by a client are large (such as when many different formats are supported by
    1213          a user-agent), proactive negotiation becomes unwieldy, and might not be appropriate. Conversely, when the number of representations
     1213         a user agent), proactive negotiation becomes unwieldy, and might not be appropriate. Conversely, when the number of representations
    12141214         to choose from is very large, reactive negotiation might not be appropriate.
    12151215      </p>
    … …  
    29542954      <h3 id="rfc.section.8.1.3"><a href="#rfc.section.8.1.3">8.1.3</a>&nbsp;<a id="header.retry-after" href="#header.retry-after">Retry-After</a></h3>
    29552955      <p id="rfc.section.8.1.3.p.1">The header "Retry-After" field can be used with a <a href="#status.503" class="smpl">503 (Service
    2956             Unavailable)</a> response to indicate how long the service is expected to be unavailable to the requesting client. This field <em class="bcp14">MAY</em> also be used with any <a href="#status.3xx" class="smpl">3xx (Redirection)</a> response to indicate the minimum time the user-agent is asked to wait before issuing the redirected request.
     2956            Unavailable)</a> response to indicate how long the service is expected to be unavailable to the requesting client. This field <em class="bcp14">MAY</em> also be used with any <a href="#status.3xx" class="smpl">3xx (Redirection)</a> response to indicate the minimum time the user agent is asked to wait before issuing the redirected request.
    29572957      </p>
    29582958      <p id="rfc.section.8.1.3.p.2">The value of this field can be either an HTTP-date or an integer number of seconds (in decimal) after the time of the response.</p>

  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1950 r1957  
    940940   and practicality. In particular, when the number of preferences or
    941941   capabilities to be expressed by a client are large (such as when many
    942    different formats are supported by a user-agent), proactive
     942   different formats are supported by a user agent), proactive
    943943   negotiation becomes unwieldy, and might not be appropriate. Conversely,
    944944   when the number of representations to choose from is very large,
    … …  
    37753775   be unavailable to the requesting client. This field &MAY; also be used
    37763776   with any <x:ref>3xx (Redirection)</x:ref> response to indicate the minimum time the
    3777    user-agent is asked to wait before issuing the redirected request.
     3777   user agent is asked to wait before issuing the redirected request.
    37783778</t>
    37793779<t>
Note: See TracChangeset for help on using the changeset viewer.