Changeset 2334 for draft-ietf-httpbis/latest/p2-semantics.xml

Timestamp:

01/08/13 10:42:01 (10 years ago)

Author:

fielding@…

Message:

Many changes to properly target MUST requirements by role; addresses #484

File:

• draft-ietf-httpbis/latest/p2-semantics.xml (modified) (3 diffs)

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

@@ -1747 +1747 @@
    would be foolish for a user agent to send stored user credentials
    <xref target="Part7"/> or cookies <xref target="RFC6265"/> in a TRACE
-   request. The final recipient &SHOULD; exclude any request header fields
-   from the response body that are likely to contain sensitive data.
+   request. The final recipient of the request &SHOULD; exclude any request
+   header fields that are likely to contain sensitive data when that recipient
+   generates the response body.
 </t>
 <t>
@@ -2481 +2482 @@
    reference for the resource from which the <x:ref>target URI</x:ref> was
    obtained (i.e., the "referrer", though the field name is misspelled).
-   A user agent &MUST; exclude any fragment or userinfo components
-   <xref target="RFC3986"/> when generating the Referer field value.
+   A user agent &MUST-NOT; include the fragment and userinfo components
+   of the URI reference <xref target="RFC3986"/>, if any, when generating the
+   Referer field value.
 </t>
 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Referer"/>
@@ -2733 +2735 @@
 </t>
 <t>
-   A client &MUST; be prepared to accept one or more 1xx status responses
+   A client &MUST; be able to parse one or more 1xx status responses received
    prior to a final response, even if the client does not expect one.
    A user agent &MAY; ignore unexpected 1xx status responses.