Ignore:
Timestamp:
01/08/13 10:42:01 (8 years ago)
Author:
fielding@…
Message:

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

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r2333 r2334  
    17471747   would be foolish for a user agent to send stored user credentials
    17481748   <xref target="Part7"/> or cookies <xref target="RFC6265"/> in a TRACE
    1749    request. The final recipient &SHOULD; exclude any request header fields
    1750    from the response body that are likely to contain sensitive data.
     1749   request. The final recipient of the request &SHOULD; exclude any request
     1750   header fields that are likely to contain sensitive data when that recipient
     1751   generates the response body.
    17511752</t>
    17521753<t>
     
    24812482   reference for the resource from which the <x:ref>target URI</x:ref> was
    24822483   obtained (i.e., the "referrer", though the field name is misspelled).
    2483    A user agent &MUST; exclude any fragment or userinfo components
    2484    <xref target="RFC3986"/> when generating the Referer field value.
     2484   A user agent &MUST-NOT; include the fragment and userinfo components
     2485   of the URI reference <xref target="RFC3986"/>, if any, when generating the
     2486   Referer field value.
    24852487</t>
    24862488<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Referer"/>
     
    27332735</t>
    27342736<t>
    2735    A client &MUST; be prepared to accept one or more 1xx status responses
     2737   A client &MUST; be able to parse one or more 1xx status responses received
    27362738   prior to a final response, even if the client does not expect one.
    27372739   A user agent &MAY; ignore unexpected 1xx status responses.
Note: See TracChangeset for help on using the changeset viewer.