Ignore:
Timestamp:
Jul 24, 2011, 11:27:10 AM (8 years ago)
Author:
julian.reschke@…
Message:

clarify not about parsing *-Authenticate header fields

File:
1 edited

Legend:

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

    r1328 r1343  
    317317<x:note>
    318318  <t>
    319    <x:h>Note:</x:h> User agents will need to take special care in parsing the WWW-Authenticate
    320    or Proxy-Authenticate header field value if it contains
    321    more than one challenge, or if more than one WWW-Authenticate header
    322    field is provided, since the contents of a challenge can itself
    323    contain a comma-separated list of authentication parameters.
     319     <x:h>Note:</x:h> User agents will need to take special care in parsing the
     320     WWW-Authenticate and Proxy-Authenticate header field values because they
     321     can contain more than one challenge, or if more than one of each is
     322     provided, since the contents of a challenge can itself contain a
     323     comma-separated list of authentication parameters.
    324324  </t>
    325325</x:note>
    326326<x:note>
    327327  <t>
    328       <x:h>Note:</x:h> Many browsers fail to parse challenges containing unknown
    329       schemes. A workaround for this problem is to list well-supported schemes
    330       (such as "basic") first.
     328     <x:h>Note:</x:h> Many browsers fail to parse challenges containing unknown
     329     schemes. A workaround for this problem is to list well-supported schemes
     330     (such as "basic") first.
    331331  </t>
    332332</x:note>
Note: See TracChangeset for help on using the changeset viewer.