Ignore:
Timestamp:
28/02/09 19:39:48 (13 years ago)
Author:
julian.reschke@…
Message:

make indentation of examples consistent

Location:
draft-ietf-httpbis/latest
Files:
6 edited

Legend:

Unmodified
Added
Removed

  • draft-ietf-httpbis/latest/p1-messaging.html

    r457 r458  
    672672         MIME-like message payloads for flexible interaction with network-based hypertext information systems. HTTP relies upon the
    673673         Uniform Resource Identifier (URI) standard <a href="#RFC3986" id="rfc.xref.RFC3986.1"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a> to indicate resource targets and relationships between resources. Messages are passed in a format similar to that used by
    674          Internet mail <a href="#RFC5322" id="rfc.xref.RFC5322.1"><cite title="Internet Message Format">[RFC5322]</cite></a> and the Multipurpose Internet Mail Extensions (MIME) <a href="#RFC2045" id="rfc.xref.RFC2045.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a> (see <a href="p3-payload.html#differences.between.http.entities.and.rfc.2045.entities" title="ERROR: Anchor 'differences.between.http.entities.and.rfc.2045.entities' not found in p3-payload.xml.">Appendix ERROR: Anchor 'differences.between.http.entities.and.rfc.2045.entities' not found in p3-payload.xml.</a> of <a href="#Part3" id="rfc.xref.Part3.1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a> for the differences between HTTP and MIME messages).
     674         Internet mail <a href="#RFC5322" id="rfc.xref.RFC5322.1"><cite title="Internet Message Format">[RFC5322]</cite></a> and the Multipurpose Internet Mail Extensions (MIME) <a href="#RFC2045" id="rfc.xref.RFC2045.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a> (see <a href="p3-payload.html#differences.between.http.entities.and.rfc.2045.entities" title="Differences Between HTTP Entities and RFC 2045 Entities">Appendix A</a> of <a href="#Part3" id="rfc.xref.Part3.1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a> for the differences between HTTP and MIME messages).
    675675      </p>
    676676      <p id="rfc.section.1.p.2">HTTP is a generic interface protocol for informations systems. It is designed to hide the details of how a service is implemented
    … …  
    733733</pre><p id="rfc.section.1.2.1.p.6">For compatibility with legacy list rules, recipients <em class="bcp14">SHOULD</em> accept empty list elements. In other words, consumers would follow the list productions:
    734734      </p>
    735       <div id="rfc.figure.u.4"></div><pre class="text">#element =&gt; [ ( "," / element ) *( OWS "," [ OWS element ] ) ]
    736 
    737 1#element =&gt; *( "," OWS ) element *( OWS "," [ OWS element ] )
     735      <div id="rfc.figure.u.4"></div><pre class="text">  #element =&gt; [ ( "," / element ) *( OWS "," [ OWS element ] ) ]
     736 
     737  1#element =&gt; *( "," OWS ) element *( OWS "," [ OWS element ] )
    738738</pre><p id="rfc.section.1.2.1.p.8"> <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;D</a> shows the collected ABNF, with the list rules expanded as explained above.
    739739      </p>
    … …  
    741741      <div id="rule.CRLF">
    742742         <p id="rfc.section.1.2.2.p.1">  HTTP/1.1 defines the sequence CR LF as the end-of-line marker for all protocol elements except the entity-body (see <a href="#tolerant.applications" title="Tolerant Applications">Appendix&nbsp;A</a> for tolerant applications). The end-of-line marker within an entity-body is defined by its associated media type, as described
    743             in <a href="p3-payload.html#media.types" title="ERROR: Anchor 'media.types' not found in p3-payload.xml.">Appendix ERROR: Anchor 'media.types' not found in p3-payload.xml.</a> of <a href="#Part3" id="rfc.xref.Part3.2"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>.
     743            in <a href="p3-payload.html#media.types" title="Media Types">Section 2.3</a> of <a href="#Part3" id="rfc.xref.Part3.2"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>.
    744744         </p>
    745745      </div>
    … …  
    793793      <div id="rfc.figure.u.9"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">request-header</a>  = &lt;request-header, defined in <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#request.header.fields" title="Request Header Fields">Section 3</a>&gt;
    794794  <a href="#abnf.dependencies" class="smpl">response-header</a> = &lt;response-header, defined in <a href="#Part2" id="rfc.xref.Part2.2"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#response.header.fields" title="Response Header Fields">Section 5</a>&gt;
    795 </pre><div id="rfc.figure.u.10"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">entity-body</a>     = &lt;entity-body, defined in <a href="#Part3" id="rfc.xref.Part3.3"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.body" title="ERROR: Anchor 'entity.body' not found in p3-payload.xml.">Appendix ERROR: Anchor 'entity.body' not found in p3-payload.xml.</a>&gt;
    796   <a href="#abnf.dependencies" class="smpl">entity-header</a>   = &lt;entity-header, defined in <a href="#Part3" id="rfc.xref.Part3.4"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.header.fields" title="ERROR: Anchor 'entity.header.fields' not found in p3-payload.xml.">Appendix ERROR: Anchor 'entity.header.fields' not found in p3-payload.xml.</a>&gt;
     795</pre><div id="rfc.figure.u.10"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">entity-body</a>     = &lt;entity-body, defined in <a href="#Part3" id="rfc.xref.Part3.3"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.body" title="Entity Body">Section 3.2</a>&gt;
     796  <a href="#abnf.dependencies" class="smpl">entity-header</a>   = &lt;entity-header, defined in <a href="#Part3" id="rfc.xref.Part3.4"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.header.fields" title="Entity Header Fields">Section 3.1</a>&gt;
    797797</pre><div id="rfc.figure.u.11"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">Cache-Control</a>   = &lt;Cache-Control, defined in <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.pragma" title="Pragma">Section 15.4</a>&gt;
    798798  <a href="#abnf.dependencies" class="smpl">Pragma</a>          = &lt;Pragma, defined in <a href="#Part6" id="rfc.xref.Part6.2"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.pragma" title="Pragma">Section 15.4</a>&gt;
    … …  
    970970      <h3 id="rfc.section.3.2.1"><a href="#rfc.section.3.2.1">3.2.1</a>&nbsp;<a id="full.date" href="#full.date">Full Date</a></h3>
    971971      <p id="rfc.section.3.2.1.p.1">HTTP applications have historically allowed three different formats for the representation of date/time stamps:</p>
    972       <div id="rfc.figure.u.19"></div><pre class="text">   Sun, 06 Nov 1994 08:49:37 GMT  ; RFC 1123
    973    Sunday, 06-Nov-94 08:49:37 GMT ; obsolete RFC 850 format
    974    Sun Nov  6 08:49:37 1994       ; ANSI C's asctime() format
     972      <div id="rfc.figure.u.19"></div><pre class="text">  Sun, 06 Nov 1994 08:49:37 GMT  ; RFC 1123
     973  Sunday, 06-Nov-94 08:49:37 GMT ; obsolete RFC 850 format
     974  Sun Nov  6 08:49:37 1994       ; ANSI C's asctime() format
    975975</pre><p id="rfc.section.3.2.1.p.3">The first format is preferred as an Internet standard and represents a fixed-length subset of that defined by <a href="#RFC1123" id="rfc.xref.RFC1123.1"><cite title="Requirements for Internet Hosts - Application and Support">[RFC1123]</cite></a>. The other formats are described here only for compatibility with obsolete implementations. HTTP/1.1 clients and servers
    976976         that parse the date value <em class="bcp14">MUST</em> accept all three formats (for compatibility with HTTP/1.0), though they <em class="bcp14">MUST</em> only generate the RFC 1123 format for representing HTTP-date values in header fields. See <a href="#tolerant.applications" title="Tolerant Applications">Appendix&nbsp;A</a> for further information.
    … …  
    10631063      </p>
    10641064      <p id="rfc.section.3.3.p.8">The Internet Assigned Numbers Authority (IANA) acts as a registry for transfer-coding value tokens. Initially, the registry
    1065          contains the following tokens: "chunked" (<a href="#chunked.transfer.encoding" title="Chunked Transfer Coding">Section&nbsp;3.3.1</a>), "gzip", "compress", and "deflate" (<a href="p3-payload.html#content.codings" title="ERROR: Anchor 'content.codings' not found in p3-payload.xml.">Appendix ERROR: Anchor 'content.codings' not found in p3-payload.xml.</a> of <a href="#Part3" id="rfc.xref.Part3.5"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>).
    1066       </p>
    1067       <p id="rfc.section.3.3.p.9">New transfer-coding value tokens <em class="bcp14">SHOULD</em> be registered in the same way as new content-coding value tokens (<a href="p3-payload.html#content.codings" title="ERROR: Anchor 'content.codings' not found in p3-payload.xml.">Appendix ERROR: Anchor 'content.codings' not found in p3-payload.xml.</a> of <a href="#Part3" id="rfc.xref.Part3.6"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>).
     1065         contains the following tokens: "chunked" (<a href="#chunked.transfer.encoding" title="Chunked Transfer Coding">Section&nbsp;3.3.1</a>), "gzip", "compress", and "deflate" (<a href="p3-payload.html#content.codings" title="Content Codings">Section 2.2</a> of <a href="#Part3" id="rfc.xref.Part3.5"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>).
     1066      </p>
     1067      <p id="rfc.section.3.3.p.9">New transfer-coding value tokens <em class="bcp14">SHOULD</em> be registered in the same way as new content-coding value tokens (<a href="p3-payload.html#content.codings" title="Content Codings">Section 2.2</a> of <a href="#Part3" id="rfc.xref.Part3.6"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>).
    10681068      </p>
    10691069      <p id="rfc.section.3.3.p.10">A server which receives an entity-body with a transfer-coding it does not understand <em class="bcp14">SHOULD</em> return 501 (Not Implemented), and close the connection. A server <em class="bcp14">MUST NOT</em> send transfer-codings to an HTTP/1.0 client.
    … …  
    11371137  <a href="#product.tokens" class="smpl">product-version</a> = <a href="#rule.token.separators" class="smpl">token</a>
    11381138</pre><p id="rfc.section.3.4.p.3">Examples:</p>
    1139       <div id="rfc.figure.u.26"></div><pre class="text">    User-Agent: CERN-LineMode/2.15 libwww/2.17b3
    1140     Server: Apache/0.8.4
     1139      <div id="rfc.figure.u.26"></div><pre class="text">  User-Agent: CERN-LineMode/2.15 libwww/2.17b3
     1140  Server: Apache/0.8.4
    11411141</pre><p id="rfc.section.3.4.p.5">Product tokens <em class="bcp14">SHOULD</em> be short and to the point. They <em class="bcp14">MUST NOT</em> be used for advertising or other non-essential information. Although any token character <em class="bcp14">MAY</em> appear in a product-version, this token <em class="bcp14">SHOULD</em> only be used for a version identifier (i.e., successive versions of the same product <em class="bcp14">SHOULD</em> only differ in the product-version portion of the product value).
    11421142      </p>
    11431143      <h2 id="rfc.section.3.5"><a href="#rfc.section.3.5">3.5</a>&nbsp;<a id="quality.values" href="#quality.values">Quality Values</a></h2>
    1144       <p id="rfc.section.3.5.p.1">Both transfer codings (TE request header, <a href="#header.te" id="rfc.xref.header.te.3" title="TE">Section&nbsp;8.5</a>) and content negotiation (<a href="p3-payload.html#content.negotiation" title="ERROR: Anchor 'content.negotiation' not found in p3-payload.xml.">Appendix ERROR: Anchor 'content.negotiation' not found in p3-payload.xml.</a> of <a href="#Part3" id="rfc.xref.Part3.7"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) use short "floating point" numbers to indicate the relative importance ("weight") of various negotiable parameters. A weight
     1144      <p id="rfc.section.3.5.p.1">Both transfer codings (TE request header, <a href="#header.te" id="rfc.xref.header.te.3" title="TE">Section&nbsp;8.5</a>) and content negotiation (<a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 4</a> of <a href="#Part3" id="rfc.xref.Part3.7"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) use short "floating point" numbers to indicate the relative importance ("weight") of various negotiable parameters. A weight
    11451145         is normalized to a real number in the range 0 through 1, where 0 is the minimum and 1 the maximum value. If a parameter has
    11461146         a quality value of 0, then content with this parameter is `not acceptable' for the client. HTTP/1.1 applications <em class="bcp14">MUST NOT</em> generate more than three digits after the decimal point. User configuration of these values <em class="bcp14">SHOULD</em> also be limited in this fashion.
    … …  
    13151315                  *(( <a href="#general.header.fields" class="smpl">general-header</a>        ; <a href="#general.header.fields" title="General Header Fields">Section&nbsp;4.5</a>
    13161316                   / <a href="#abnf.dependencies" class="smpl">request-header</a>         ; <a href="#Part2" id="rfc.xref.Part2.4"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#request.header.fields" title="Request Header Fields">Section 3</a>
    1317                    / <a href="#abnf.dependencies" class="smpl">entity-header</a> ) <a href="#core.rules" class="smpl">CRLF</a> )  ; <a href="#Part3" id="rfc.xref.Part3.8"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.header.fields" title="ERROR: Anchor 'entity.header.fields' not found in p3-payload.xml.">Appendix ERROR: Anchor 'entity.header.fields' not found in p3-payload.xml.</a>
     1317                   / <a href="#abnf.dependencies" class="smpl">entity-header</a> ) <a href="#core.rules" class="smpl">CRLF</a> )  ; <a href="#Part3" id="rfc.xref.Part3.8"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.header.fields" title="Entity Header Fields">Section 3.1</a>
    13181318                  <a href="#core.rules" class="smpl">CRLF</a>
    13191319                  [ <a href="#message.body" class="smpl">message-body</a> ]          ; <a href="#message.body" title="Message Body">Section&nbsp;4.3</a>
    … …  
    14081408                  *(( <a href="#general.header.fields" class="smpl">general-header</a>        ; <a href="#general.header.fields" title="General Header Fields">Section&nbsp;4.5</a>
    14091409                   / <a href="#abnf.dependencies" class="smpl">response-header</a>        ; <a href="#Part2" id="rfc.xref.Part2.7"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#response.header.fields" title="Response Header Fields">Section 5</a>
    1410                    / <a href="#abnf.dependencies" class="smpl">entity-header</a> ) <a href="#core.rules" class="smpl">CRLF</a> )  ; <a href="#Part3" id="rfc.xref.Part3.9"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.header.fields" title="ERROR: Anchor 'entity.header.fields' not found in p3-payload.xml.">Appendix ERROR: Anchor 'entity.header.fields' not found in p3-payload.xml.</a>
     1410                   / <a href="#abnf.dependencies" class="smpl">entity-header</a> ) <a href="#core.rules" class="smpl">CRLF</a> )  ; <a href="#Part3" id="rfc.xref.Part3.9"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.header.fields" title="Entity Header Fields">Section 3.1</a>
    14111411                  <a href="#core.rules" class="smpl">CRLF</a>
    14121412                  [ <a href="#message.body" class="smpl">message-body</a> ]          ; <a href="#message.body" title="Message Body">Section&nbsp;4.3</a>
    … …  
    25392539      </p>
    25402540      <dl class="empty">
    2541          <dd>The mechanism for selecting the appropriate representation when servicing a request, as described in <a href="p3-payload.html#content.negotiation" title="ERROR: Anchor 'content.negotiation' not found in p3-payload.xml.">Appendix ERROR: Anchor 'content.negotiation' not found in p3-payload.xml.</a> of <a href="#Part3" id="rfc.xref.Part3.12"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. The representation of entities in any response can be negotiated (including error responses).
     2541         <dd>The mechanism for selecting the appropriate representation when servicing a request, as described in <a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 4</a> of <a href="#Part3" id="rfc.xref.Part3.12"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. The representation of entities in any response can be negotiated (including error responses).
    25422542         </dd>
    25432543      </dl>
    … …  
    25462546      <dl class="empty">
    25472547         <dd>The information transferred as the payload of a request or response. An entity consists of metainformation in the form of
    2548             entity-header fields and content in the form of an entity-body, as described in <a href="p3-payload.html#entity" title="ERROR: Anchor 'entity' not found in p3-payload.xml.">Appendix ERROR: Anchor 'entity' not found in p3-payload.xml.</a> of <a href="#Part3" id="rfc.xref.Part3.13"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>.
     2548            entity-header fields and content in the form of an entity-body, as described in <a href="p3-payload.html#entity" title="Entity">Section 3</a> of <a href="#Part3" id="rfc.xref.Part3.13"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>.
    25492549         </dd>
    25502550      </dl>
    … …  
    26072607      </p>
    26082608      <dl class="empty">
    2609          <dd>An entity included with a response that is subject to content negotiation, as described in <a href="p3-payload.html#content.negotiation" title="ERROR: Anchor 'content.negotiation' not found in p3-payload.xml.">Appendix ERROR: Anchor 'content.negotiation' not found in p3-payload.xml.</a> of <a href="#Part3" id="rfc.xref.Part3.14"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. There may exist multiple representations associated with a particular response status.
     2609         <dd>An entity included with a response that is subject to content negotiation, as described in <a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 4</a> of <a href="#Part3" id="rfc.xref.Part3.14"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>. There may exist multiple representations associated with a particular response status.
    26102610         </dd>
    26112611      </dl>
    … …  
    32243224                  </li>
    32253225                  <li class="indline1"><em>Part3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.1">1</a>, <a class="iref" href="#rfc.xref.Part3.2">1.2.2</a>, <a class="iref" href="#rfc.xref.Part3.3">1.2.3</a>, <a class="iref" href="#rfc.xref.Part3.4">1.2.3</a>, <a class="iref" href="#rfc.xref.Part3.5">3.3</a>, <a class="iref" href="#rfc.xref.Part3.6">3.3</a>, <a class="iref" href="#rfc.xref.Part3.7">3.5</a>, <a class="iref" href="#rfc.xref.Part3.8">5</a>, <a class="iref" href="#rfc.xref.Part3.9">6</a>, <a class="iref" href="#Part3"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.Part3.10">A</a>, <a class="iref" href="#rfc.xref.Part3.11">B.3</a>, <a class="iref" href="#rfc.xref.Part3.12">C</a>, <a class="iref" href="#rfc.xref.Part3.13">C</a>, <a class="iref" href="#rfc.xref.Part3.14">C</a><ul class="ind">
    3226                         <li class="indline1"><em>Appendix </em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.1">1</a></li>
    3227                         <li class="indline1"><em>Appendix </em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.2">1.2.2</a></li>
    3228                         <li class="indline1"><em>Appendix </em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.3">1.2.3</a></li>
    3229                         <li class="indline1"><em>Appendix </em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.4">1.2.3</a>, <a class="iref" href="#rfc.xref.Part3.8">5</a>, <a class="iref" href="#rfc.xref.Part3.9">6</a></li>
    3230                         <li class="indline1"><em>Appendix </em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.5">3.3</a>, <a class="iref" href="#rfc.xref.Part3.6">3.3</a></li>
    3231                         <li class="indline1"><em>Appendix </em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.7">3.5</a>, <a class="iref" href="#rfc.xref.Part3.12">C</a>, <a class="iref" href="#rfc.xref.Part3.14">C</a></li>
    3232                         <li class="indline1"><em>Appendix </em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.13">C</a></li>
     3226                        <li class="indline1"><em>Section 2.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.5">3.3</a>, <a class="iref" href="#rfc.xref.Part3.6">3.3</a></li>
     3227                        <li class="indline1"><em>Section 2.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.2">1.2.2</a></li>
     3228                        <li class="indline1"><em>Section 3.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.4">1.2.3</a>, <a class="iref" href="#rfc.xref.Part3.8">5</a>, <a class="iref" href="#rfc.xref.Part3.9">6</a></li>
     3229                        <li class="indline1"><em>Section 3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.13">C</a></li>
     3230                        <li class="indline1"><em>Section 3.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.3">1.2.3</a></li>
     3231                        <li class="indline1"><em>Section 4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.7">3.5</a>, <a class="iref" href="#rfc.xref.Part3.12">C</a>, <a class="iref" href="#rfc.xref.Part3.14">C</a></li>
     3232                        <li class="indline1"><em>Appendix A</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.1">1</a></li>
    32333233                     </ul>
    32343234                  </li>

  • draft-ietf-httpbis/latest/p1-messaging.xml

    r457 r458  
    369369  </t>
    370370<figure><artwork type="example">
    371 #element =&gt; [ ( "," / element ) *( OWS "," [ OWS element ] ) ]
    372 
    373 1#element =&gt; *( "," OWS ) element *( OWS "," [ OWS element ] )
     371  #element =&gt; [ ( "," / element ) *( OWS "," [ OWS element ] ) ]
     372 
     373  1#element =&gt; *( "," OWS ) element *( OWS "," [ OWS element ] )
    374374</artwork></figure> 
    375375<t>
    … …  
    853853</t>
    854854<figure><artwork type="example">
    855    Sun, 06 Nov 1994 08:49:37 GMT  ; RFC 1123
    856    Sunday, 06-Nov-94 08:49:37 GMT ; obsolete RFC 850 format
    857    Sun Nov  6 08:49:37 1994       ; ANSI C's asctime() format
     855  Sun, 06 Nov 1994 08:49:37 GMT  ; RFC 1123
     856  Sunday, 06-Nov-94 08:49:37 GMT ; obsolete RFC 850 format
     857  Sun Nov  6 08:49:37 1994       ; ANSI C's asctime() format
    858858</artwork></figure>
    859859<t>
    … …  
    11301130</t>
    11311131<figure><artwork type="example">
    1132     User-Agent: CERN-LineMode/2.15 libwww/2.17b3
    1133     Server: Apache/0.8.4
     1132  User-Agent: CERN-LineMode/2.15 libwww/2.17b3
     1133  Server: Apache/0.8.4
    11341134</artwork></figure>
    11351135<t>

  • 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.

  • draft-ietf-httpbis/latest/p3-payload.xml

    r457 r458  
    634634</t>
    635635<figure><artwork type="example">
    636     en, en-US, en-cockney, i-cherokee, x-pig-latin
     636  en, en-US, en-cockney, i-cherokee, x-pig-latin
    637637</artwork></figure>
    638638<t>
    … …  
    710710</t>
    711711<figure><artwork type="example">
    712     entity-body := Content-Encoding( Content-Type( data ) )
     712  entity-body := Content-Encoding( Content-Type( data ) )
    713713</artwork></figure>
    714714<t>
    … …  
    25692569</t>
    25702570<figure><artwork type="example">
    2571    Content-Disposition: attachment; filename="fname.ext"
     2571  Content-Disposition: attachment; filename="fname.ext"
    25722572</artwork></figure>
    25732573<t>

  • draft-ietf-httpbis/latest/p6-cache.html

    r454 r458  
    982982         than the one for the existing entry, then the client <em class="bcp14">SHOULD</em> repeat the request unconditionally, and include
    983983      </p>
    984       <div id="rfc.figure.u.9"></div><pre class="text">    Cache-Control: max-age=0
     984      <div id="rfc.figure.u.9"></div><pre class="text">  Cache-Control: max-age=0
    985985</pre><p id="rfc.section.3.6.p.5">to force any intermediate caches to validate their copies directly with the origin server, or</p>
    986       <div id="rfc.figure.u.10"></div><pre class="text">    Cache-Control: no-cache
     986      <div id="rfc.figure.u.10"></div><pre class="text">  Cache-Control: no-cache
    987987</pre><p id="rfc.section.3.6.p.7">to force any intermediate caches to obtain a new copy from the origin server.</p>
    988988      <p id="rfc.section.3.6.p.8">If the Date values are equal, then the client <em class="bcp14">MAY</em> use either response (or <em class="bcp14">MAY</em>, if it is being extremely prudent, request a new response). Servers <em class="bcp14">MUST NOT</em> depend on clients being able to choose deterministically between responses generated during the same second, if their expiration
    … …  
    15591559         an otherwise private response in their shared cache(s) could do so by including
    15601560      </p>
    1561       <div id="rfc.figure.u.14"></div><pre class="text">    Cache-Control: private, community="UCI"
     1561      <div id="rfc.figure.u.14"></div><pre class="text">  Cache-Control: private, community="UCI"
    15621562</pre><p id="rfc.section.15.2.6.p.5">A cache seeing this header field will act correctly even if the cache does not understand the community cache-extension, since
    15631563         it will also see and understand the private directive and thus default to the safe behavior.

  • draft-ietf-httpbis/latest/p6-cache.xml

    r454 r458  
    994994</t>
    995995<figure><artwork type="example">
    996     Cache-Control: max-age=0
     996  Cache-Control: max-age=0
    997997</artwork></figure>
    998998<t>
    … …  
    10011001</t>
    10021002<figure><artwork type="example">
    1003     Cache-Control: no-cache
     1003  Cache-Control: no-cache
    10041004</artwork></figure>
    10051005<t>
    … …  
    20872087</t>
    20882088<figure><artwork type="example">
    2089     Cache-Control: private, community="UCI"
     2089  Cache-Control: private, community="UCI"
    20902090</artwork></figure>
    20912091<t>
Note: See TracChangeset for help on using the changeset viewer.