Ignore:
Timestamp:
Feb 28, 2009, 11:39:48 AM (11 years ago)
Author:
julian.reschke@…
Message:

make indentation of examples consistent

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p3-payload.html

    r457 r458  
    815815         by the IANA. Example tags include:
    816816      </p>
    817       <div id="rfc.figure.u.11"></div><pre class="text">    en, en-US, en-cockney, i-cherokee, x-pig-latin
     817      <div id="rfc.figure.u.11"></div><pre class="text">  en, en-US, en-cockney, i-cherokee, x-pig-latin
    818818</pre><p id="rfc.section.2.4.p.6">where any two-letter primary-tag is an ISO-639 language abbreviation and any two-letter initial subtag is an ISO-3166 country
    819819         code. (The last three tags above are not registered tags; all but the last are examples of tags which could be registered
     
    856856         and Content-Encoding. These define a two-layer, ordered encoding model:
    857857      </p>
    858       <div id="rfc.figure.u.14"></div><pre class="text">    entity-body := Content-Encoding( Content-Type( data ) )
     858      <div id="rfc.figure.u.14"></div><pre class="text">  entity-body := Content-Encoding( Content-Type( data ) )
    859859</pre><p id="rfc.section.3.2.1.p.3">Content-Type specifies the media type of the underlying data. Content-Encoding may be used to indicate any additional content
    860860         codings applied to the data, usually for the purpose of data compression, that are a property of the requested resource. There
     
    16571657  <a href="#content-disposition" class="smpl">disp-extension-parm</a> = <a href="#core.rules" class="smpl">token</a> "=" ( <a href="#core.rules" class="smpl">token</a> / <a href="#core.rules" class="smpl">quoted-string</a> )
    16581658</pre><p id="rfc.section.B.1.p.3">An example is</p>
    1659       <div id="rfc.figure.u.39"></div><pre class="text">   Content-Disposition: attachment; filename="fname.ext"
     1659      <div id="rfc.figure.u.39"></div><pre class="text">  Content-Disposition: attachment; filename="fname.ext"
    16601660</pre><p id="rfc.section.B.1.p.5">The receiving user agent <em class="bcp14">SHOULD NOT</em> respect any directory path information present in the filename-parm parameter, which is the only parameter believed to apply
    16611661         to HTTP implementations at this time. The filename <em class="bcp14">SHOULD</em> be treated as a terminal component only.
Note: See TracChangeset for help on using the changeset viewer.