Ignore:
Timestamp:
Jul 8, 2012, 11:15:03 AM (7 years ago)
Author:
julian.reschke@…
Message:

Work-in-progress: hyperlink header field definitions, plus minor editorial improvements (P2)

File:
1 edited

Legend:

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

    r1736 r1740  
    173173   impact on security. This is because different uses of the protocol require
    174174   different error handling strategies; for example, a Web browser might wish to
    175    transparently recover from a response where the Location header field
    176    doesn't parse according to the ABNF, whereby in a systems control protocol
    177    using HTTP, this type of error recovery could lead to dangerous consequences.
     175   transparently recover from a response where the <x:ref>Location</x:ref>
     176   header field doesn't parse according to the ABNF, whereby in a systems
     177   control protocol using HTTP, this type of error recovery could lead to
     178   dangerous consequences.
    178179</t>
    179180</section>
     
    325326   credentials or contain invalid or partial credentials, a proxy &SHOULD;
    326327   return a <x:ref>407 (Proxy Authentication Required)</x:ref> response. Such responses
    327    &MUST; include a <x:ref>Proxy-Authenticate header</x:ref> field containing a (possibly
     328   &MUST; include a <x:ref>Proxy-Authenticate</x:ref> header field containing a (possibly
    328329   new) challenge applicable to the proxy.
    329330</t>
     
    896897  <x:source basename="p2-semantics" href="p2-semantics.xml">
    897898    <x:defines>403 (Forbidden)</x:defines>
     899    <x:defines>Location</x:defines>
    898900  </x:source>
    899901</reference>
Note: See TracChangeset for help on using the changeset viewer.