Ignore:
Timestamp:
04/11/10 09:27:49 (9 years ago)
Author:
julian.reschke@…
Message:

fix typo (see #263)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis-content-disp/latest/draft-ietf-httpbis-content-disp.html

    r1076 r1077  
    800800      <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a>&nbsp;<a id="alternatives.percent" href="#alternatives.percent">Percent Encoding</a></h2>
    801801      <p id="rfc.section.C.2.p.1">Some user agents accept percent encoded (<a href="#RFC3986" id="rfc.xref.RFC3986.1"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-2.1">Section 2.1</a>) sequences of characters. The character encoding being used for decoding depends on various factors, including the encoding
    802          of the referring page, the user agent's locale, it's configuration, and also the actual value of the parameter.
     802         of the referring page, the user agent's locale, its configuration, and also the actual value of the parameter.
    803803      </p>
    804804      <p id="rfc.section.C.2.p.2">In practice, this is hard to use because those user agents that do not support it will display the escaped character sequence
Note: See TracChangeset for help on using the changeset viewer.