Changeset 148 for draft-ietf-httpbis

Timestamp:

05/01/08 02:43:02 (13 years ago)

Author:

fielding@…

Message:

Fix remaining Misc. Typos to address #50.

Location:

draft-ietf-httpbis/latest

Files:

• p1-messaging.html (modified) (1 diff)
• p1-messaging.xml (modified) (1 diff)
• p3-payload.html (modified) (1 diff)
• p3-payload.xml (modified) (1 diff)
• p6-cache.html (modified) (1 diff)
• p6-cache.xml (modified) (1 diff)

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

@@ -1686 +1686 @@
       <div id="rfc.figure.u.44"></div><pre class="text">    GET /pub/WWW/ HTTP/1.1
     Host: www.example.org
-</pre><p id="rfc.section.8.4.p.5">A client <em class="bcp14">MUST</em> include a Host header field in all HTTP/1.1 request messages . If the requested URI does not include an Internet host name
+</pre><p id="rfc.section.8.4.p.5">A client <em class="bcp14">MUST</em> include a Host header field in all HTTP/1.1 request messages. If the requested URI does not include an Internet host name
          for the service being requested, then the Host header field <em class="bcp14">MUST</em> be given with an empty value. An HTTP/1.1 proxy <em class="bcp14">MUST</em> ensure that any request message it forwards does contain an appropriate Host header field that identifies the service being
          requested by the proxy. All Internet-based HTTP/1.1 servers <em class="bcp14">MUST</em> respond with a 400 (Bad Request) status code to any HTTP/1.1 request message which lacks a Host header field.

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

@@ -2392 +2392 @@
 <t>
    A client &MUST; include a Host header field in all HTTP/1.1 request
-   messages . If the requested URI does not include an Internet host
+   messages. If the requested URI does not include an Internet host
    name for the service being requested, then the Host header field &MUST;
    be given with an empty value. An HTTP/1.1 proxy &MUST; ensure that any

draft-ietf-httpbis/latest/p3-payload.html

@@ -750 +750 @@
       <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a id="entity.header.fields" href="#entity.header.fields">Entity Header Fields</a></h2>
       <p id="rfc.section.3.1.p.1">Entity-header fields define metainformation about the entity-body or, if no body is present, about the resource identified
-         by the request. Some of this metainformation is <em class="bcp14">OPTIONAL</em>; some might be <em class="bcp14">REQUIRED</em> by portions of this specification.
+         by the request.
       </p>
       <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span>  entity-header  = Allow                    ; <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#header.allow" title="Allow">Section 10.1</a>

draft-ietf-httpbis/latest/p3-payload.xml

@@ -578 +578 @@
    Entity-header fields define metainformation about the entity-body or,
    if no body is present, about the resource identified by the request.
-   Some of this metainformation is &OPTIONAL;; some might be &REQUIRED; by
-   portions of this specification.
 </t>
 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="entity-header"/><iref primary="true" item="Grammar" subitem="extension-header"/>

draft-ietf-httpbis/latest/p6-cache.html

@@ -1595 +1595 @@
       </p>
       <dl class="empty">
-         <dd> <b>Note:</b> because the meaning of "Pragma: no-cache as a response header field is not actually specified, it does not provide a reliable
-            replacement for "Cache-Control: no-cache" in a response
+         <dd> <b>Note:</b> because the meaning of "Pragma: no-cache" as a response-header field is not actually specified, it does not provide a reliable
+            replacement for "Cache-Control: no-cache" in a response.
          </dd>
       </dl>

draft-ietf-httpbis/latest/p6-cache.xml

@@ -2208 +2208 @@
    defined in HTTP.
   <list><t>
-      <x:h>Note:</x:h> because the meaning of "Pragma: no-cache as a response
-      header field is not actually specified, it does not provide a
-      reliable replacement for "Cache-Control: no-cache" in a response
+      <x:h>Note:</x:h> because the meaning of "Pragma: no-cache" as a
+      response-header field is not actually specified, it does not provide a
+      reliable replacement for "Cache-Control: no-cache" in a response.
   </t></list>
 </t>