Ignore:
Timestamp:
Jun 23, 2012, 5:01:38 AM (7 years ago)
Author:
julian.reschke@…
Message:

Simplify use of "Note:", make upper/lowercase of sentence start consistent; use "—" where appropriate

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p7-auth.xml

    r1689 r1692  
    1616  <!ENTITY ID-YEAR "2012">
    1717  <!ENTITY mdash "&#8212;">
     18  <!ENTITY Note "<x:h xmlns:x='http://purl.org/net/xml2rfc/ext'>Note:</x:h>">
    1819  <!ENTITY architecture                 "<xref target='Part1' x:rel='#architecture' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    1920  <!ENTITY notation                     "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     
    272273<x:note>
    273274  <t>
    274      <x:h>Note:</x:h> User agents will need to take special care in parsing the
     275     &Note; User agents will need to take special care in parsing the
    275276     WWW-Authenticate and Proxy-Authenticate header field values because they
    276277     can contain more than one challenge, or if more than one of each is
     
    281282<x:note>
    282283  <t>
    283      <x:h>Note:</x:h> Many clients fail to parse challenges containing unknown
     284     &Note; Many clients fail to parse challenges containing unknown
    284285     schemes. A workaround for this problem is to list well-supported schemes
    285286     (such as "basic") first.<!-- see http://greenbytes.de/tech/tc/httpauth/#multibasicunknown2 -->
     
    447448    </t>
    448449    <t>
    449       <x:h>Note:</x:h> the fact that the value syntax for the "realm" parameter
     450      &Note; The fact that the value syntax for the "realm" parameter
    450451      is restricted to quoted-string was a bad design choice not to be repeated
    451452      for new parameters.
     
    675676<x:note>
    676677  <t>
    677     <x:h>Note:</x:h> The challenge grammar production uses the list syntax as
     678    &Note; The challenge grammar production uses the list syntax as
    678679    well. Therefore, a sequence of comma, whitespace, and comma can be
    679680    considered both as applying to the preceding challenge, or to be an
Note: See TracChangeset for help on using the changeset viewer.