Changeset 2197


Ignore:
Timestamp:
Mar 3, 2013, 11:06:21 AM (6 years ago)
Author:
julian.reschke@…
Message:

minor grammar fixes

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

Legend:

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

    r2195 r2197  
    449449  }
    450450  @bottom-center {
    451        content: "Expires September 2, 2013";
     451       content: "Expires September 4, 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="2013-03-01">
     493      <meta name="dct.issued" scheme="ISO8601" content="2013-03-03">
    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">March 1, 2013</td>
     522               <td class="right">March 3, 2013</td>
    523523            </tr>
    524524            <tr>
    525                <td class="left">Expires: September 2, 2013</td>
     525               <td class="left">Expires: September 4, 2013</td>
    526526               <td class="right"></td>
    527527            </tr>
     
    551551         in progress”.
    552552      </p>
    553       <p>This Internet-Draft will expire on September 2, 2013.</p>
     553      <p>This Internet-Draft will expire on September 4, 2013.</p>
    554554      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    555555      <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    12091209         the protocol version if their defined semantics allow them to be safely ignored by recipients that do not recognize them.
    12101210      </p>
    1211       <p id="rfc.section.3.2.1.p.2">New HTTP header fields ought to be be registered with IANA in the Message Header Field Registry, as described in <a href="p2-semantics.html#header.field.registry" title="Header Field Registry">Section 8.3</a> of <a href="#Part2" id="rfc.xref.Part2.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>. A proxy <em class="bcp14">MUST</em> forward unrecognized header fields unless the field-name is listed in the <a href="#header.connection" class="smpl">Connection</a> header field (<a href="#header.connection" id="rfc.xref.header.connection.3" title="Connection">Section&nbsp;6.1</a>) or the proxy is specifically configured to block, or otherwise transform, such fields. Other recipients <em class="bcp14">SHOULD</em> ignore unrecognized header fields.
     1211      <p id="rfc.section.3.2.1.p.2">New HTTP header fields ought to be registered with IANA in the Message Header Field Registry, as described in <a href="p2-semantics.html#header.field.registry" title="Header Field Registry">Section 8.3</a> of <a href="#Part2" id="rfc.xref.Part2.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>. A proxy <em class="bcp14">MUST</em> forward unrecognized header fields unless the field-name is listed in the <a href="#header.connection" class="smpl">Connection</a> header field (<a href="#header.connection" id="rfc.xref.header.connection.3" title="Connection">Section&nbsp;6.1</a>) or the proxy is specifically configured to block, or otherwise transform, such fields. Other recipients <em class="bcp14">SHOULD</em> ignore unrecognized header fields.
    12121212      </p>
    12131213      <h3 id="rfc.section.3.2.2"><a href="#rfc.section.3.2.2">3.2.2</a>&nbsp;<a id="field.order" href="#field.order">Field Order</a></h3>
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r2195 r2197  
    11991199</t>
    12001200<t>
    1201    New HTTP header fields ought to be be registered with IANA in the
     1201   New HTTP header fields ought to be registered with IANA in the
    12021202   Message Header Field Registry, as described in &iana-header-registry;.
    12031203   A proxy &MUST; forward unrecognized header fields unless the
  • draft-ietf-httpbis/latest/p2-semantics.html

    r2196 r2197  
    13881388         is just as likely to be implemented as a tree of content objects, a programmatic view on various database records, or a gateway
    13891389         to other information systems. Even when the URI mapping mechanism is tied to a filesystem, an origin server might be configured
    1390          to execute the files with the request as input and send the output as the representation, rather then transfer the files directly.
    1391          Regardless, only the origin server needs to know how each of its resource identifiers correspond to an implementation, and
     1390         to execute the files with the request as input and send the output as the representation, rather than transfer the files directly.
     1391         Regardless, only the origin server needs to know how each of its resource identifiers corresponds to an implementation, and
    13921392         how each implementation manages to select and send a current representation of the target resource in a response to GET.
    13931393      </p>
     
    18521852         all subtypes of that type. The media-range can include media type parameters that are applicable to that range.
    18531853      </p>
    1854       <p id="rfc.section.5.3.2.p.4">Each media-range might be followed by zero or more applicable media type parameters (e.g., <a href="#charset" class="smpl">charset</a>), an optional "q" parameter for indicating a relative weight (<a href="#quality.values" title="Quality Values">Section&nbsp;5.3.1</a>), and then zero or more extension parameters. The "q" parameter is necessary if any accept-ext are present, since it acts
    1855          as a separator between the two parameter sets.
     1854      <p id="rfc.section.5.3.2.p.4">Each media-range might be followed by zero or more applicable media type parameters (e.g., <a href="#charset" class="smpl">charset</a>), an optional "q" parameter for indicating a relative weight (<a href="#quality.values" title="Quality Values">Section&nbsp;5.3.1</a>), and then zero or more extension parameters. The "q" parameter is necessary if any extensions (accept-ext) are present,
     1855         since it acts as a separator between the two parameter sets.
    18561856      </p>
    18571857      <div class="note" id="rfc.section.5.3.2.p.5">
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r2196 r2197  
    12681268   other information systems. Even when the URI mapping mechanism is tied to a
    12691269   filesystem, an origin server might be configured to execute the files with
    1270    the request as input and send the output as the representation, rather then
     1270   the request as input and send the output as the representation, rather than
    12711271   transfer the files directly. Regardless, only the origin server needs to
    1272    know how each of its resource identifiers correspond to an implementation,
     1272   know how each of its resource identifiers corresponds to an implementation,
    12731273   and how each implementation manages to select and send a current
    12741274   representation of the target resource in a response to GET.
     
    20932093   parameters (e.g., <x:ref>charset</x:ref>), an optional "q" parameter for
    20942094   indicating a relative weight (&qvalue;), and then zero or more extension
    2095    parameters. The "q" parameter is necessary if any accept-ext are present,
     2095   parameters. The "q" parameter is necessary if any extensions (accept-ext) are present,
    20962096   since it acts as a separator between the two parameter sets.
    20972097</t>
Note: See TracChangeset for help on using the changeset viewer.