Changeset 1776


Ignore:
Timestamp:
Jul 14, 2012, 10:52:23 AM (7 years ago)
Author:
julian.reschke@…
Message:

spelling fixes

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

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p0-introduction.html

    r1772 r1776  
    523523         known as HTTP/1.1.
    524524      </p>
    525       <p id="rfc.section.1.p.2">The document series is organised as follows:</p>
     525      <p id="rfc.section.1.p.2">The document series is organized as follows:</p>
    526526      <ul>
    527527         <li>HTTP/1.1 Introduction - this document</li>
  • draft-ietf-httpbis/latest/p0-introduction.xml

    r1772 r1776  
    128128   HTTP/1.1.
    129129</t>
    130 <t>The document series is organised as follows:</t>
     130<t>The document series is organized as follows:</t>
    131131<t><list style="symbols">
    132132   <t>HTTP/1.1 Introduction - this document</t>
  • draft-ietf-httpbis/latest/p1-messaging.html

    r1773 r1776  
    15221522      </p>
    15231523      <h2 id="rfc.section.3.4"><a href="#rfc.section.3.4">3.4</a>&nbsp;<a id="incomplete.messages" href="#incomplete.messages">Handling Incomplete Messages</a></h2>
    1524       <p id="rfc.section.3.4.p.1">Request messages that are prematurely terminated, possibly due to a cancelled connection or a server-imposed time-out exception, <em class="bcp14">MUST</em> result in closure of the connection; sending an HTTP/1.1 error response prior to closing the connection is <em class="bcp14">OPTIONAL</em>.
     1524      <p id="rfc.section.3.4.p.1">Request messages that are prematurely terminated, possibly due to a canceled connection or a server-imposed time-out exception, <em class="bcp14">MUST</em> result in closure of the connection; sending an HTTP/1.1 error response prior to closing the connection is <em class="bcp14">OPTIONAL</em>.
    15251525      </p>
    15261526      <p id="rfc.section.3.4.p.2">Response messages that are prematurely terminated, usually by closure of the connection prior to receiving the expected number
     
    26322632      <p id="rfc.section.8.1.p.1">HTTP clients are often privy to large amounts of personal information (e.g., the user's name, location, mail address, passwords,
    26332633         encryption keys, etc.), and <em class="bcp14">SHOULD</em> be very careful to prevent unintentional leakage of this information. We very strongly recommend that a convenient interface
    2634          be provided for the user to control dissemination of such information, and that designers and implementors be particularly
     2634         be provided for the user to control dissemination of such information, and that designers and implementers be particularly
    26352635         careful in this area. History shows that errors in this area often create serious security and/or privacy problems and generate
    2636          highly adverse publicity for the implementor's company.
     2636         highly adverse publicity for the implementer's company.
    26372637      </p>
    26382638      <h2 id="rfc.section.8.2"><a href="#rfc.section.8.2">8.2</a>&nbsp;<a id="abuse.of.server.log.information" href="#abuse.of.server.log.information">Abuse of Server Log Information</a></h2>
     
    26732673      </p>
    26742674      <p id="rfc.section.8.5.p.2">Intermediaries that contain a shared cache are especially vulnerable to cache poisoning attacks.</p>
    2675       <p id="rfc.section.8.5.p.3">Implementors need to consider the privacy and security implications of their design and coding decisions, and of the configuration
     2675      <p id="rfc.section.8.5.p.3">Implementers need to consider the privacy and security implications of their design and coding decisions, and of the configuration
    26762676         options they provide to operators (especially the default configuration).
    26772677      </p>
     
    29922992      </p>
    29932993      <h2 id="rfc.section.A.2"><a href="#rfc.section.A.2">A.2</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2>
    2994       <p id="rfc.section.A.2.p.1">Clarify that the string "HTTP" in the HTTP-version ABFN production is case sensitive. Restrict the version numbers to be single
     2994      <p id="rfc.section.A.2.p.1">Clarify that the string "HTTP" in the HTTP-version ABNF production is case sensitive. Restrict the version numbers to be single
    29952995         digits due to the fact that implementations are known to handle multi-digit version numbers incorrectly. (<a href="#http.version" title="Protocol Versioning">Section&nbsp;2.7</a>)
    29962996      </p>
     
    30213021         Remove requirements about when servers are allowed to close connections prematurely. (<a href="#persistent.practical" title="Practical Considerations">Section&nbsp;6.3.3</a>)
    30223022      </p>
    3023       <p id="rfc.section.A.2.p.12">Remove requirement to retry requests under certain cirumstances when the server prematurely closes the connection. (<a href="#message.transmission.requirements" title="Message Transmission Requirements">Section&nbsp;6.4</a>)
     3023      <p id="rfc.section.A.2.p.12">Remove requirement to retry requests under certain circumstances when the server prematurely closes the connection. (<a href="#message.transmission.requirements" title="Message Transmission Requirements">Section&nbsp;6.4</a>)
    30243024      </p>
    30253025      <p id="rfc.section.A.2.p.13">Change ABNF productions for header fields to only define the field value.</p>
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r1773 r1776  
    18211821<t>
    18221822   Request messages that are prematurely terminated, possibly due to a
    1823    cancelled connection or a server-imposed time-out exception, &MUST;
     1823   canceled connection or a server-imposed time-out exception, &MUST;
    18241824   result in closure of the connection; sending an HTTP/1.1 error response
    18251825   prior to closing the connection is &OPTIONAL;.
     
    37733773   We very strongly recommend that a convenient interface be provided
    37743774   for the user to control dissemination of such information, and that
    3775    designers and implementors be particularly careful in this area.
     3775   designers and implementers be particularly careful in this area.
    37763776   History shows that errors in this area often create serious security
    37773777   and/or privacy problems and generate highly adverse publicity for the
    3778    implementor's company.
     3778   implementer's company.
    37793779</t>
    37803780</section>
     
    38563856</t>
    38573857<t>
    3858    Implementors need to consider the privacy and security
     3858   Implementers need to consider the privacy and security
    38593859   implications of their design and coding decisions, and of the
    38603860   configuration options they provide to operators (especially the
     
    50105010<section title="Changes from RFC 2616" anchor="changes.from.rfc.2616">
    50115011<t>
    5012   Clarify that the string "HTTP" in the HTTP-version ABFN production is case
     5012  Clarify that the string "HTTP" in the HTTP-version ABNF production is case
    50135013  sensitive. Restrict the version numbers to be single digits due to the fact
    50145014  that implementations are known to handle multi-digit version numbers
     
    50715071</t>
    50725072<t>
    5073   Remove requirement to retry requests under certain cirumstances when the
     5073  Remove requirement to retry requests under certain circumstances when the
    50745074  server prematurely closes the connection.
    50755075  (<xref target="message.transmission.requirements"/>)
  • draft-ietf-httpbis/latest/p2-semantics.html

    r1774 r1776  
    899899      <div id="rfc.iref.s.2"></div>
    900900      <h3 id="rfc.section.2.1.1"><a href="#rfc.section.2.1.1">2.1.1</a>&nbsp;<a id="safe.methods" href="#safe.methods">Safe Methods</a></h3>
    901       <p id="rfc.section.2.1.1.p.1">Implementors need to be aware that the software represents the user in their interactions over the Internet, and need to allow
     901      <p id="rfc.section.2.1.1.p.1">Implementers need to be aware that the software represents the user in their interactions over the Internet, and need to allow
    902902         the user to be aware of any actions they take which might have an unexpected significance to themselves or others.
    903903      </p>
     
    20822082      </p>
    20832083      <div class="note" id="rfc.section.4.7.5.p.2">
    2084          <p> <b>Note</b> to implementors: some deployed proxies are known to return <a href="#status.400" class="smpl">400 (Bad Request)</a> or <a href="#status.500" class="smpl">500 (Internal Server
     2084         <p> <b>Note</b> to implementers: some deployed proxies are known to return <a href="#status.400" class="smpl">400 (Bad Request)</a> or <a href="#status.500" class="smpl">500 (Internal Server
    20852085               Error)</a> when DNS lookups time out.
    20862086         </p>
     
    22052205      <p id="rfc.section.5.3.p.5">HTTP uses charset in two contexts: within an <a href="#header.accept-charset" class="smpl">Accept-Charset</a> request header field (in which the charset value is an unquoted token) and as the value of a parameter in a <a href="#header.content-type" class="smpl">Content-Type</a> header field (within a request or response), in which case the parameter value of the charset parameter can be quoted.
    22062206      </p>
    2207       <p id="rfc.section.5.3.p.6">Implementors need to be aware of IETF character set requirements <a href="#RFC3629" id="rfc.xref.RFC3629.1"><cite title="UTF-8, a transformation format of ISO 10646">[RFC3629]</cite></a>  <a href="#RFC2277" id="rfc.xref.RFC2277.1"><cite title="IETF Policy on Character Sets and Languages">[RFC2277]</cite></a>.
     2207      <p id="rfc.section.5.3.p.6">Implementers need to be aware of IETF character set requirements <a href="#RFC3629" id="rfc.xref.RFC3629.1"><cite title="UTF-8, a transformation format of ISO 10646">[RFC3629]</cite></a>  <a href="#RFC2277" id="rfc.xref.RFC2277.1"><cite title="IETF Policy on Character Sets and Languages">[RFC2277]</cite></a>.
    22082208      </p>
    22092209      <h2 id="rfc.section.5.4"><a href="#rfc.section.5.4">5.4</a>&nbsp;<a id="content.codings" href="#content.codings">Content Codings</a></h2>
     
    27632763      </p>
    27642764      <div class="note" id="rfc.section.9.4.p.10">
    2765          <p> <b>Note:</b> When making the choice of linguistic preference available to the user, we remind implementors of the fact that users are not
     2765         <p> <b>Note:</b> When making the choice of linguistic preference available to the user, we remind implementers of the fact that users are not
    27662766            familiar with the details of language matching as described above, and ought to be provided appropriate guidance. As an example,
    27672767            users might assume that on selecting "en-gb", they will be served any kind of English document if British English is not available.
     
    30583058      <div class="note" id="rfc.section.9.17.p.7">
    30593059         <p> <b>Note:</b> Revealing the specific software version of the server might allow the server machine to become more vulnerable to attacks
    3060             against software that is known to contain security holes. Server implementors are encouraged to make this field a configurable
     3060            against software that is known to contain security holes. Server implementers are encouraged to make this field a configurable
    30613061            option.
    30623062         </p>
     
    36053605      </p>
    36063606      <p id="rfc.section.11.1.p.2">Revealing the specific software version of the server might allow the server machine to become more vulnerable to attacks
    3607          against software that is known to contain security holes. Implementors <em class="bcp14">SHOULD</em> make the <a href="#header.server" class="smpl">Server</a> header field a configurable option.
     3607         against software that is known to contain security holes. Implementers <em class="bcp14">SHOULD</em> make the <a href="#header.server" class="smpl">Server</a> header field a configurable option.
    36083608      </p>
    36093609      <p id="rfc.section.11.1.p.3">Proxies which serve as a portal through a network firewall <em class="bcp14">SHOULD</em> take special precautions regarding the transfer of header information that identifies the hosts behind the firewall. In particular,
     
    39343934      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="additional.features" href="#additional.features">Additional Features</a></h1>
    39353935      <p id="rfc.section.B.p.1"> <a href="#RFC1945" id="rfc.xref.RFC1945.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.0">[RFC1945]</cite></a> and <a href="#RFC2068" id="rfc.xref.RFC2068.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a> document protocol elements used by some existing HTTP implementations, but not consistently and correctly across most HTTP/1.1
    3936          applications. Implementors are advised to be aware of these features, but cannot rely upon their presence in, or interoperability
     3936         applications. Implementers are advised to be aware of these features, but cannot rely upon their presence in, or interoperability
    39373937         with, other HTTP/1.1 applications. Some of these describe proposed experimental features, and some describe features that
    39383938         experimental deployment found lacking that are now addressed in the base HTTP/1.1 specification.
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1774 r1776  
    417417<iref item="Safe Methods" primary="true"/>
    418418<t>
    419    Implementors need to be aware that the software represents the user in
     419   Implementers need to be aware that the software represents the user in
    420420   their interactions over the Internet, and need to allow
    421421   the user to be aware of any actions they take which might have an
     
    21742174<x:note>
    21752175  <t>
    2176     <x:h>Note</x:h> to implementors: some deployed proxies are known to
     2176    <x:h>Note</x:h> to implementers: some deployed proxies are known to
    21772177    return <x:ref>400 (Bad Request)</x:ref> or <x:ref>500 (Internal Server
    21782178    Error)</x:ref> when DNS lookups time out.
     
    24052405</t>
    24062406<t>
    2407    Implementors need to be aware of IETF character set requirements <xref target="RFC3629"/>
     2407   Implementers need to be aware of IETF character set requirements <xref target="RFC3629"/>
    24082408   <xref target="RFC2277"/>.
    24092409</t>
     
    33283328  <t>
    33293329    &Note; When making the choice of linguistic preference available to
    3330     the user, we remind implementors of  the fact that users are not
     3330    the user, we remind implementers of  the fact that users are not
    33313331    familiar with the details of language matching as described above,
    33323332    and ought to be provided appropriate guidance. As an example, users
     
    39613961    allow the server machine to become more vulnerable to attacks
    39623962    against software that is known to contain security holes. Server
    3963     implementors are encouraged to make this field a configurable
     3963    implementers are encouraged to make this field a configurable
    39643964    option.
    39653965  </t>
     
    44854485   Revealing the specific software version of the server might allow the
    44864486   server machine to become more vulnerable to attacks against software
    4487    that is known to contain security holes. Implementors &SHOULD; make the
     4487   that is known to contain security holes. Implementers &SHOULD; make the
    44884488   <x:ref>Server</x:ref> header field a configurable option.
    44894489</t>
     
    54755475   <xref target="RFC1945"/> and <xref target="RFC2068"/> document protocol elements used by some
    54765476   existing HTTP implementations, but not consistently and correctly
    5477    across most HTTP/1.1 applications. Implementors are advised to be
     5477   across most HTTP/1.1 applications. Implementers are advised to be
    54785478   aware of these features, but cannot rely upon their presence in, or
    54795479   interoperability with, other HTTP/1.1 applications. Some of these
  • draft-ietf-httpbis/latest/p5-range.html

    r1773 r1776  
    653653      </ul>
    654654      <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="introduction" href="#introduction">Introduction</a></h1>
    655       <p id="rfc.section.1.p.1">HTTP clients often encounter interrupted data transfers as a result of cancelled requests or dropped connections. When a client
     655      <p id="rfc.section.1.p.1">HTTP clients often encounter interrupted data transfers as a result of canceled requests or dropped connections. When a client
    656656         has stored a partial representation, it is desirable to request the remainder of that representation in a subsequent request
    657657         rather than transfer the entire representation. There are also a number of Web applications that benefit from being able to
  • draft-ietf-httpbis/latest/p5-range.xml

    r1773 r1776  
    133133<t>
    134134   HTTP clients often encounter interrupted data transfers as a result
    135    of cancelled requests or dropped connections.  When a client has stored
     135   of canceled requests or dropped connections.  When a client has stored
    136136   a partial representation, it is desirable to request the remainder
    137137   of that representation in a subsequent request rather than transfer
  • draft-ietf-httpbis/latest/p6-cache.html

    r1775 r1776  
    20482048         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/355">http://tools.ietf.org/wg/httpbis/trac/ticket/355</a>&gt;: "Case sensitivity of header fields in CC values"
    20492049         </li>
    2050          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/356">http://tools.ietf.org/wg/httpbis/trac/ticket/356</a>&gt;: "Spurious 'MAY's"
     2050         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/356">http://tools.ietf.org/wg/httpbis/trac/ticket/356</a>&gt;: "Spurious 'MAYs'"
    20512051         </li>
    20522052         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/360">http://tools.ietf.org/wg/httpbis/trac/ticket/360</a>&gt;: "enhance considerations for new cache control directives"
  • draft-ietf-httpbis/latest/p6-cache.xml

    r1775 r1776  
    26742674    <t>
    26752675      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/356"/>:
    2676       "Spurious 'MAY's"
     2676      "Spurious 'MAYs'"
    26772677    </t>
    26782678    <t>
Note: See TracChangeset for help on using the changeset viewer.