Ignore:
Timestamp:
Aug 4, 2010, 8:03:20 AM (9 years ago)
Author:
julian.reschke@…
Message:

regen HTML using latest version of xslt

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/orig/rfc2145.html

    r598 r978  
    4747}
    4848
    49 dl.empty dd {
     49ul.empty {
     50  list-style-type: none;
     51}
     52ul.empty li {
    5053  margin-top: .5em;
    5154}
     
    128131}
    129132table.header {
     133  border-spacing: 1px;
    130134  width: 95%;
    131135  font-size: 10pt;
     
    139143  white-space: nowrap;
    140144}
    141 td.header {
     145table.header td {
    142146  background-color: gray;
    143147  width: 50%;
     
    315319      <link rel="Alternate" title="Authorative ASCII Version" href="http://www.ietf.org/rfc/rfc2145.txt">
    316320      <link rel="Help" title="Additional Information on tools.ietf.org" href="http://tools.ietf.org/html/rfc2145">
    317       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.438, 2009-05-27 13:34:05, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
     321      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.520, 2010-07-14 12:36:35, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    318322      <meta name="keywords" content="HTTP, hypertext transfer protocol">
    319       <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/">
    320       <meta name="DC.Creator" content="Mogul, J. C.">
    321       <meta name="DC.Creator" content="Fielding, R. T.">
    322       <meta name="DC.Creator" content="Gettys, J.">
    323       <meta name="DC.Creator" content="Frystyk, H.">
    324       <meta name="DC.Identifier" content="urn:ietf:rfc:2145">
    325       <meta name="DC.Date.Issued" scheme="ISO8601" content="1997-05">
    326       <meta name="DC.Description.Abstract" content="HTTP request and response messages include an HTTP protocol version number. Some confusion exists concerning the proper use and interpretation of HTTP version numbers, and concerning interoperability of HTTP implementations of different protocol versions. This document is an attempt to clarify the situation. It is not a modification of the intended meaning of the existing HTTP/1.0 and HTTP/1.1 documents, but it does describe the intention of the authors of those documents, and can be considered definitive when there is any ambiguity in those documents concerning HTTP version numbers, for all versions of HTTP.">
    327       <meta name="DC.isPartOf" content="urn:ISSN:2070-1721">
     323      <link rel="schema.dct" href="http://purl.org/dc/terms/">
     324      <meta name="dct.creator" content="Mogul, J. C.">
     325      <meta name="dct.creator" content="Fielding, R. T.">
     326      <meta name="dct.creator" content="Gettys, J.">
     327      <meta name="dct.creator" content="Frystyk, H.">
     328      <meta name="dct.identifier" content="urn:ietf:rfc:2145">
     329      <meta name="dct.issued" scheme="ISO8601" content="1997-05">
     330      <meta name="dct.abstract" content="HTTP request and response messages include an HTTP protocol version number. Some confusion exists concerning the proper use and interpretation of HTTP version numbers, and concerning interoperability of HTTP implementations of different protocol versions. This document is an attempt to clarify the situation. It is not a modification of the intended meaning of the existing HTTP/1.0 and HTTP/1.1 documents, but it does describe the intention of the authors of those documents, and can be considered definitive when there is any ambiguity in those documents concerning HTTP version numbers, for all versions of HTTP.">
     331      <meta name="dct.isPartOf" content="urn:issn:2070-1721">
     332      <meta name="description" content="HTTP request and response messages include an HTTP protocol version number. Some confusion exists concerning the proper use and interpretation of HTTP version numbers, and concerning interoperability of HTTP implementations of different protocol versions. This document is an attempt to clarify the situation. It is not a modification of the intended meaning of the existing HTTP/1.0 and HTTP/1.1 documents, but it does describe the intention of the authors of those documents, and can be considered definitive when there is any ambiguity in those documents concerning HTTP version numbers, for all versions of HTTP.">
    328333   </head>
    329334   <body>
    330       <table summary="header information" class="header" border="0" cellpadding="1" cellspacing="1">
    331          <tr>
    332             <td class="header left">Network Working Group</td>
    333             <td class="header right">J. C. Mogul</td>
    334          </tr>
    335          <tr>
    336             <td class="header left">Request for Comments: 2145</td>
    337             <td class="header right">DEC</td>
    338          </tr>
    339          <tr>
    340             <td class="header left">Category: Informational</td>
    341             <td class="header right">R. T. Fielding</td>
    342          </tr>
    343          <tr>
    344             <td class="header left"></td>
    345             <td class="header right">UC Irvine</td>
    346          </tr>
    347          <tr>
    348             <td class="header left"></td>
    349             <td class="header right">J. Gettys</td>
    350          </tr>
    351          <tr>
    352             <td class="header left"></td>
    353             <td class="header right">DEC</td>
    354          </tr>
    355          <tr>
    356             <td class="header left"></td>
    357             <td class="header right">H. Frystyk</td>
    358          </tr>
    359          <tr>
    360             <td class="header left"></td>
    361             <td class="header right">MIT/LCS</td>
    362          </tr>
    363          <tr>
    364             <td class="header left"></td>
    365             <td class="header right">May 1997</td>
    366          </tr>
     335      <table class="header">
     336         <tbody>
     337            <tr>
     338               <td class="left">Network Working Group</td>
     339               <td class="right">J. Mogul</td>
     340            </tr>
     341            <tr>
     342               <td class="left">Request for Comments: 2145</td>
     343               <td class="right">DEC</td>
     344            </tr>
     345            <tr>
     346               <td class="left">Category: Informational</td>
     347               <td class="right">R. Fielding</td>
     348            </tr>
     349            <tr>
     350               <td class="left"></td>
     351               <td class="right">UC Irvine</td>
     352            </tr>
     353            <tr>
     354               <td class="left"></td>
     355               <td class="right">J. Gettys</td>
     356            </tr>
     357            <tr>
     358               <td class="left"></td>
     359               <td class="right">DEC</td>
     360            </tr>
     361            <tr>
     362               <td class="left"></td>
     363               <td class="right">H. Frystyk</td>
     364            </tr>
     365            <tr>
     366               <td class="left"></td>
     367               <td class="right">MIT/LCS</td>
     368            </tr>
     369            <tr>
     370               <td class="left"></td>
     371               <td class="right">May 1997</td>
     372            </tr>
     373         </tbody>
    367374      </table>
    368375      <p class="title">Use and Interpretation of HTTP Version Numbers</p>
     
    452459      <p id="rfc.section.2.p.1">We start by restating the language quoted above from section <a href="http://tools.ietf.org/html/rfc2068#section-3.1">3.1</a> of the HTTP/1.1 specification <a href="#RFC2068"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[2]</cite></a>:
    453460      </p>
    454       <dl class="empty">
    455          <dd>It is, and has always been, the explicit intent of the HTTP specification that the interpretation of an HTTP message header
     461      <ul class="empty">
     462         <li>It is, and has always been, the explicit intent of the HTTP specification that the interpretation of an HTTP message header
    456463            does not change between minor versions of the same major version.
    457          </dd>
    458          <dd>It is, and has always been, the explicit intent of the HTTP specification that an implementation receiving a message header
     464         </li>
     465         <li>It is, and has always been, the explicit intent of the HTTP specification that an implementation receiving a message header
    459466            that it does not understand <em class="bcp14">MUST</em> ignore that header. (The word "ignore" has a special meaning for proxies; see section <a href="#proxy.behavior" title="Proxy behavior">2.1</a> below.)
    460          </dd>
    461       </dl>
     467         </li>
     468      </ul>
    462469      <p id="rfc.section.2.p.2">To make this as clear as possible: The major version sent in a message <em class="bcp14">MAY</em> indicate the interpretation of other header fields. The minor version sent in a message <em class="bcp14">MUST NOT</em> indicate the interpretation of other header fields. This reflects the principle that the minor version labels the capability
    463470         of the sender, not the interpretation of the message.
    464471      </p>
    465       <div class="note">
     472      <div class="note" id="rfc.section.2.p.3">
    466473         <p>Note: In a future version of HTTP, we may introduce a mechanism that explicitly requires a receiving implementation to reject
    467474            a message if it does not understand certain headers. For example, this might be implemented by means of a header that lists
     
    520527      <h1 class="np" id="rfc.references"><a href="#rfc.section.4" id="rfc.section.4">4.</a> References
    521528      </h1>
    522       <table summary="References">
     529      <table>
    523530         <tr>
    524531            <td class="reference"><b id="RFC1945">[1]</b></td>
    525             <td class="top"><a href="mailto:timbl@w3.org" title="MIT, Laboratory for Computer Science">Berners-Lee, T.</a>, <a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine, Department of Information and Computer Science">Fielding, R.T.</a>, and <a href="mailto:frystyk@w3.org" title="W3 Consortium, MIT Laboratory for Computer Science">H.F. Nielsen</a>, “<a href="http://tools.ietf.org/html/rfc1945">Hypertext Transfer Protocol -- HTTP/1.0</a>”, RFC&nbsp;1945, May&nbsp;1996.
     532            <td class="top"><a href="mailto:timbl@w3.org" title="MIT, Laboratory for Computer Science">Berners-Lee, T.</a>, <a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine, Department of Information and Computer Science">Fielding, R.</a>, and <a href="mailto:frystyk@w3.org" title="W3 Consortium, MIT Laboratory for Computer Science">H. Nielsen</a>, “<a href="http://tools.ietf.org/html/rfc1945">Hypertext Transfer Protocol -- HTTP/1.0</a>”, RFC&nbsp;1945, May&nbsp;1996.
    526533            </td>
    527534         </tr> 
     
    543550      </table>
    544551      <hr class="noprint">
    545       <h1 id="rfc.authors" class="np"><a href="#rfc.section.5" id="rfc.section.5">5.</a> <a href="#rfc.authors">Authors' Addresses</a></h1>
    546       <address class="vcard"><span class="vcardline"><span class="fn">Jeffrey C. Mogul</span><span class="n hidden"><span class="family-name">Mogul</span><span class="given-name">Jeffrey C.</span></span></span><span class="org vcardline">Western Research Laboratory</span><span class="adr"><span class="street-address vcardline">Digital Equipment Corporation</span><span class="street-address vcardline">250 University Avenue</span><span class="vcardline"><span class="locality">Palo Alto</span>, <span class="region">California</span>&nbsp;<span class="postal-code">94305</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a href="mailto:mogul@wrl.dec.com"><span class="email">mogul@wrl.dec.com</span></a></span></address>
    547       <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span><span class="n hidden"><span class="family-name">Fielding</span><span class="given-name">Roy T.</span></span></span><span class="org vcardline">Department of Information and Computer Science</span><span class="adr"><span class="street-address vcardline">University of California</span><span class="vcardline"><span class="locality">Irvine</span>, <span class="region">CA</span>&nbsp;<span class="postal-code">92717-3425</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+1(714)824-4056"><span class="value">+1 (714) 824-4056</span></a></span><span class="vcardline">EMail: <a href="mailto:fielding@ics.uci.edu"><span class="email">fielding@ics.uci.edu</span></a></span></address>
    548       <address class="vcard"><span class="vcardline"><span class="fn">Jim Gettys</span><span class="n hidden"><span class="family-name">Gettys</span><span class="given-name">Jim</span></span></span><span class="org vcardline">MIT Laboratory for Computer Science</span><span class="adr"><span class="street-address vcardline">545 Technology Square</span><span class="vcardline"><span class="locality">Cambridge</span>, <span class="region">MA</span>&nbsp;<span class="postal-code">02139</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+1(617)2588682"><span class="value">+1 (617) 258 8682</span></a></span><span class="vcardline">EMail: <a href="mailto:jg@w3.org"><span class="email">jg@w3.org</span></a></span></address>
    549       <address class="vcard"><span class="vcardline"><span class="fn">Henrik Frystyk Nielsen</span><span class="n hidden"><span class="family-name">Frystyk</span></span></span><span class="org vcardline">W3 Consortium</span><span class="adr"><span class="street-address vcardline">MIT Laboratory for Computer Science</span><span class="street-address vcardline">545 Technology Square</span><span class="vcardline"><span class="locality">Cambridge</span>, <span class="region">MA</span>&nbsp;<span class="postal-code">02139</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+1(617)2588682"><span class="value">+1 (617) 258 8682</span></a></span><span class="vcardline">EMail: <a href="mailto:frystyk@w3.org"><span class="email">frystyk@w3.org</span></a></span></address>
     552      <div class="avoidbreak">
     553         <h1 id="rfc.authors" class="np"><a href="#rfc.section.5" id="rfc.section.5">5.</a> <a href="#rfc.authors">Authors' Addresses</a></h1>
     554         <address class="vcard"><span class="vcardline"><span class="fn">Jeffrey C. Mogul</span><span class="n hidden"><span class="family-name">Mogul</span><span class="given-name">Jeffrey C.</span></span></span><span class="org vcardline">Western Research Laboratory</span><span class="adr"><span class="street-address vcardline">Digital Equipment Corporation</span><span class="street-address vcardline">250 University Avenue</span><span class="vcardline"><span class="locality">Palo Alto</span>, <span class="region">California</span>&nbsp;<span class="postal-code">94305</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a href="mailto:mogul@wrl.dec.com"><span class="email">mogul@wrl.dec.com</span></a></span></address>
     555         <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span><span class="n hidden"><span class="family-name">Fielding</span><span class="given-name">Roy T.</span></span></span><span class="org vcardline">Department of Information and Computer Science</span><span class="adr"><span class="street-address vcardline">University of California</span><span class="vcardline"><span class="locality">Irvine</span>, <span class="region">CA</span>&nbsp;<span class="postal-code">92717-3425</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+1(714)824-4056"><span class="value">+1 (714) 824-4056</span></a></span><span class="vcardline">EMail: <a href="mailto:fielding@ics.uci.edu"><span class="email">fielding@ics.uci.edu</span></a></span></address>
     556         <address class="vcard"><span class="vcardline"><span class="fn">Jim Gettys</span><span class="n hidden"><span class="family-name">Gettys</span><span class="given-name">Jim</span></span></span><span class="org vcardline">MIT Laboratory for Computer Science</span><span class="adr"><span class="street-address vcardline">545 Technology Square</span><span class="vcardline"><span class="locality">Cambridge</span>, <span class="region">MA</span>&nbsp;<span class="postal-code">02139</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+1(617)2588682"><span class="value">+1 (617) 258 8682</span></a></span><span class="vcardline">EMail: <a href="mailto:jg@w3.org"><span class="email">jg@w3.org</span></a></span></address>
     557         <address class="vcard"><span class="vcardline"><span class="fn">Henrik Frystyk Nielsen</span><span class="n hidden"><span class="family-name">Frystyk</span></span></span><span class="org vcardline">W3 Consortium</span><span class="adr"><span class="street-address vcardline">MIT Laboratory for Computer Science</span><span class="street-address vcardline">545 Technology Square</span><span class="vcardline"><span class="locality">Cambridge</span>, <span class="region">MA</span>&nbsp;<span class="postal-code">02139</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+1(617)2588682"><span class="value">+1 (617) 258 8682</span></a></span><span class="vcardline">EMail: <a href="mailto:frystyk@w3.org"><span class="email">frystyk@w3.org</span></a></span></address>
     558      </div>
    550559      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
    551560      <p>Copyright © The Internet Society (1997). All Rights Reserved.</p>
     
    558567         translate it into languages other than English.
    559568      </p>
    560       <p>The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assignees.</p>
     569      <p>The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.</p>
    561570      <p>This document and the information contained herein is provided on an “AS IS” basis and THE INTERNET SOCIETY AND THE INTERNET
    562571         ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE
Note: See TracChangeset for help on using the changeset viewer.