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/rfc2965.html

    r598 r978  
    3737}
    3838
    39 dl.empty dd {
     39ul.empty {
     40  list-style-type: none;
     41}
     42ul.empty li {
    4043  margin-top: .5em;
    4144}
     
    118121}
    119122table.header {
     123  border-spacing: 1px;
    120124  width: 95%;
    121125  font-size: 10pt;
     
    129133  white-space: nowrap;
    130134}
    131 td.header {
     135table.header td {
    132136  background-color: gray;
    133137  width: 50%;
    134138}
    135 td.header a {
     139table.header a {
    136140  color: white;
    137141}
     
    188192  margin-left: 0em;
    189193  margin-right: 0em;
     194}
     195.avoidbreak {
     196  page-break-inside: avoid;
    190197}
    191198.bcp14 {
     
    332339      <link rel="Alternate" title="Authorative ASCII Version" href="http://www.ietf.org/rfc/rfc2965.txt">
    333340      <link rel="Help" title="Additional Information on tools.ietf.org" href="http://tools.ietf.org/html/rfc2965">
    334       <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/">
    335       <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/">
    336       <meta name="DC.Creator" content="Kristol, D. M.">
    337       <meta name="DC.Creator" content="Montulli, L.">
    338       <meta name="DC.Identifier" content="urn:ietf:rfc:2965">
    339       <meta name="DC.Date.Issued" scheme="ISO8601" content="2000-10">
    340       <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2109">
    341       <meta name="DC.Description.Abstract" content="This document specifies a way to create a stateful session with Hypertext Transfer Protocol (HTTP) requests and responses. It describes three new headers, Cookie, Cookie2, and Set-Cookie2, which carry state information between participating origin servers and user agents. The method described here differs from Netscape's Cookie proposal , but it can interoperate with HTTP/1.0 user agents that use Netscape's method. (See the HISTORICAL section.) This document reflects implementation experience with RFC 2109 and obsoletes it.">
    342       <meta name="DC.isPartOf" content="urn:ISSN:2070-1721">
     341      <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/">
     342      <link rel="schema.dct" href="http://purl.org/dc/terms/">
     343      <meta name="dct.creator" content="Kristol, D. M.">
     344      <meta name="dct.creator" content="Montulli, L.">
     345      <meta name="dct.identifier" content="urn:ietf:rfc:2965">
     346      <meta name="dct.issued" scheme="ISO8601" content="2000-10">
     347      <meta name="dct.replaces" content="urn:ietf:rfc:2109">
     348      <meta name="dct.abstract" content="This document specifies a way to create a stateful session with Hypertext Transfer Protocol (HTTP) requests and responses. It describes three new headers, Cookie, Cookie2, and Set-Cookie2, which carry state information between participating origin servers and user agents. The method described here differs from Netscape's Cookie proposal , but it can interoperate with HTTP/1.0 user agents that use Netscape's method. (See the HISTORICAL section.) This document reflects implementation experience with RFC 2109 and obsoletes it.">
     349      <meta name="dct.isPartOf" content="urn:issn:2070-1721">
     350      <meta name="description" content="This document specifies a way to create a stateful session with Hypertext Transfer Protocol (HTTP) requests and responses. It describes three new headers, Cookie, Cookie2, and Set-Cookie2, which carry state information between participating origin servers and user agents. The method described here differs from Netscape's Cookie proposal , but it can interoperate with HTTP/1.0 user agents that use Netscape's method. (See the HISTORICAL section.) This document reflects implementation experience with RFC 2109 and obsoletes it.">
    343351   </head>
    344352   <body>
    345       <table summary="header information" class="header" border="0" cellpadding="1" cellspacing="1">
    346          <tr>
    347             <td class="header left">Network Working Group</td>
    348             <td class="header right">D. M. Kristol</td>
    349          </tr>
    350          <tr>
    351             <td class="header left">Request for Comments: 2965</td>
    352             <td class="header right">Bell Laboratories, Lucent Technologies</td>
    353          </tr>
    354          <tr>
    355             <td class="header left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2109">2109</a></td>
    356             <td class="header right">L. Montulli</td>
    357          </tr>
    358          <tr>
    359             <td class="header left">Category: Standards Track</td>
    360             <td class="header right">Epinions.com, Inc.</td>
    361          </tr>
    362          <tr>
    363             <td class="header left"></td>
    364             <td class="header right">October 2000</td>
    365          </tr>
     353      <table class="header">
     354         <tbody>
     355            <tr>
     356               <td class="left">Network Working Group</td>
     357               <td class="right">D. Kristol</td>
     358            </tr>
     359            <tr>
     360               <td class="left">Request for Comments: 2965</td>
     361               <td class="right">Bell Laboratories, Lucent Technologies</td>
     362            </tr>
     363            <tr>
     364               <td class="left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2109">2109</a></td>
     365               <td class="right">L. Montulli</td>
     366            </tr>
     367            <tr>
     368               <td class="left">Category: Standards Track</td>
     369               <td class="right">Epinions.com, Inc.</td>
     370            </tr>
     371            <tr>
     372               <td class="left"></td>
     373               <td class="right">October 2000</td>
     374            </tr>
     375         </tbody>
    366376      </table>
    367377      <p class="title">HTTP State Management Mechanism</p>
     
    444454         <li class="tocline0">11.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a></li>
    445455         <li class="tocline0"><a href="#rfc.authors">Authors' Addresses</a></li>
     456         <li class="tocline0"><a href="#rfc.index">Index</a></li>
    446457         <li class="tocline0"><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li>
    447          <li class="tocline0"><a href="#rfc.index">Index</a></li>
    448458      </ul>
    449459      <hr class="noprint">
     
    810820domain          =  "$Domain" "=" value
    811821port            =  "$Port" [ "=" &lt;"&gt; value &lt;"&gt; ]
    812 </pre>
    813       <!--WARNING: artwork line too long: 'cookie          =  "Cookie:" cookie-version 1*((";" | ",") cookie-value)' (72 characters)--><p id="rfc.section.3.3.4.p.3">The value of the cookie-version attribute <em class="bcp14">MUST</em> be the value from the Version attribute of the corresponding Set-Cookie2 response header. Otherwise the value for cookie-version
     822</pre><p id="rfc.section.3.3.4.p.3">The value of the cookie-version attribute <em class="bcp14">MUST</em> be the value from the Version attribute of the corresponding Set-Cookie2 response header. Otherwise the value for cookie-version
    814823         is 0. The value for the path attribute <em class="bcp14">MUST</em> be the value from the Path attribute, if one was present, of the corresponding Set-Cookie2 response header. Otherwise the
    815824         attribute <em class="bcp14">SHOULD</em> be omitted from the Cookie request header. The value for the domain attribute <em class="bcp14">MUST</em> be the value from the Domain attribute, if one was present, of the corresponding Set-Cookie2 response header. Otherwise the
     
    12221231      <h1 class="np" id="rfc.references"><a href="#rfc.section.11" id="rfc.section.11">11.</a> References
    12231232      </h1>
    1224       <table summary="References">
     1233      <table>
    12251234         <tr>
    12261235            <td class="reference"><b id="DMK95">[DMK95]</b></td>
    1227             <td class="top">Kristol, D. M., “<a href="http://portal.research.bell-labs.com/~dmk/state-info.html">Proposed HTTP State-Info Mechanism</a>”, September&nbsp;1995, &lt;<a href="http://portal.research.bell-labs.com/~dmk/state-info.html">http://portal.research.bell-labs.com/~dmk/state-info.html</a>&gt;.<br>available at &lt;http://portal.research.bell-labs.com/~dmk/state-info.html&gt;
     1236            <td class="top">Kristol, D., “<a href="http://portal.research.bell-labs.com/~dmk/state-info.html">Proposed HTTP State-Info Mechanism</a>”, September&nbsp;1995, &lt;<a href="http://portal.research.bell-labs.com/~dmk/state-info.html">http://portal.research.bell-labs.com/~dmk/state-info.html</a>&gt;.<br>available at &lt;http://portal.research.bell-labs.com/~dmk/state-info.html&gt;
    12281237            </td>
    12291238         </tr> 
     
    12331242            </td>
    12341243         </tr> 
    1235          <!--WARNING: unused reference 'RFC2109'-->
    12361244         <tr>
    12371245            <td class="reference"><b id="RFC2109">[RFC2109]</b></td>
    1238             <td class="top"><a href="mailto:dmk@bell-labs.com" title="Bell Laboratories, Lucent Technologies">Kristol, D.M.</a> and <a href="mailto:montulli@netscape.com" title="Netscape Communications Corp.">L. Montulli</a>, “<a href="http://tools.ietf.org/html/rfc2109">HTTP State Management Mechanism</a>”, RFC&nbsp;2109, February&nbsp;1997.
     1246            <td class="top"><a href="mailto:dmk@bell-labs.com" title="Bell Laboratories, Lucent Technologies">Kristol, D.</a> and <a href="mailto:montulli@netscape.com" title="Netscape Communications Corp.">L. Montulli</a>, “<a href="http://tools.ietf.org/html/rfc2109">HTTP State Management Mechanism</a>”, RFC&nbsp;2109, February&nbsp;1997.
    12391247            </td>
    12401248         </tr> 
     
    12511259         <tr>
    12521260            <td class="reference"><b id="RFC2396">[RFC2396]</b></td>
    1253             <td class="top"><a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:fielding@ics.uci.edu" title="Department of Information and Computer Science">Fielding, R.T.</a>, and <a href="mailto:masinter@parc.xerox.com" title="Xerox PARC">L. Masinter</a>, “<a href="http://tools.ietf.org/html/rfc2396">Uniform Resource Identifiers (URI): Generic Syntax</a>”, RFC&nbsp;2396, August&nbsp;1998.
     1261            <td class="top"><a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:fielding@ics.uci.edu" title="Department of Information and Computer Science">Fielding, R.</a>, and <a href="mailto:masinter@parc.xerox.com" title="Xerox PARC">L. Masinter</a>, “<a href="http://tools.ietf.org/html/rfc2396">Uniform Resource Identifiers (URI): Generic Syntax</a>”, RFC&nbsp;2396, August&nbsp;1998.
    12541262            </td>
    12551263         </tr> 
     
    12611269      </table>
    12621270      <hr class="noprint">
    1263       <h1 id="rfc.authors" class="np"><a href="#rfc.authors">Authors' Addresses</a></h1>
    1264       <address class="vcard"><span class="vcardline"><span class="fn">David M. Kristol</span><span class="n hidden"><span class="family-name">Kristol</span><span class="given-name">David M.</span></span></span><span class="org vcardline">Bell Laboratories, Lucent Technologies</span><span class="adr"><span class="street-address vcardline">600 Mountain Ave.  Room 2A-333</span><span class="vcardline"><span class="locality">Murray Hill</span>, <span class="region">NJ</span>&nbsp;<span class="postal-code">07974</span></span></span><span class="vcardline tel">Phone: <a href="tel:(908)582-2250"><span class="value">(908) 582-2250</span></a></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:(908)582-1239"><span class="value">(908) 582-1239</span></a></span><span class="vcardline">EMail: <a href="mailto:dmk@bell-labs.com"><span class="email">dmk@bell-labs.com</span></a></span></address>
    1265       <address class="vcard"><span class="vcardline"><span class="fn">Lou Montulli</span><span class="n hidden"><span class="family-name">Montulli</span><span class="given-name">Lou</span></span></span><span class="org vcardline">Epinions.com, Inc.</span><span class="adr"><span class="street-address vcardline">2037 Landings Dr.</span><span class="vcardline"><span class="locality">Mountain View</span>, <span class="region">CA</span>&nbsp;<span class="postal-code">94301</span></span></span><span class="vcardline">EMail: <a href="mailto:lou@montulli.org"><span class="email">lou@montulli.org</span></a></span></address>
    1266       <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
    1267       <p>Copyright © The Internet Society (2000). All Rights Reserved.</p>
    1268       <p>This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise
    1269          explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without
    1270          restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative
    1271          works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references
    1272          to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards
    1273          in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to
    1274          translate it into languages other than English.
    1275       </p>
    1276       <p>The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assignees.</p>
    1277       <p>This document and the information contained herein is provided on an “AS IS” basis and THE INTERNET SOCIETY AND THE INTERNET
    1278          ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE
    1279          OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR
    1280          PURPOSE.
    1281       </p>
    1282       <hr class="noprint">
    1283       <h1 class="np"><a id="rfc.ipr" href="#rfc.ipr">Intellectual Property</a></h1>
    1284       <p>The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed
    1285          to pertain to the implementation or use of the technology described in this document or the extent to which any license under
    1286          such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights.
    1287          Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be
    1288          found in BCP-11. Copies of claims of rights made available for publication and any assurances of licenses to be made available,
    1289          or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors
    1290          or users of this specification can be obtained from the IETF Secretariat.
    1291       </p>
    1292       <p>The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary
    1293          rights which may cover technology that may be required to practice this standard. Please address the information to the IETF
    1294          Executive Director.
    1295       </p>
    1296       <h1>Acknowledgment</h1>
    1297       <p>Funding for the RFC Editor function is currently provided by the Internet Society.</p>
     1271      <div class="avoidbreak">
     1272         <h1 id="rfc.authors" class="np"><a href="#rfc.authors">Authors' Addresses</a></h1>
     1273         <address class="vcard"><span class="vcardline"><span class="fn">David M. Kristol</span><span class="n hidden"><span class="family-name">Kristol</span><span class="given-name">David M.</span></span></span><span class="org vcardline">Bell Laboratories, Lucent Technologies</span><span class="adr"><span class="street-address vcardline">600 Mountain Ave. Room 2A-333</span><span class="vcardline"><span class="locality">Murray Hill</span>, <span class="region">NJ</span>&nbsp;<span class="postal-code">07974</span></span></span><span class="vcardline tel">Phone: <a href="tel:(908)582-2250"><span class="value">(908) 582-2250</span></a></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:(908)582-1239"><span class="value">(908) 582-1239</span></a></span><span class="vcardline">EMail: <a href="mailto:dmk@bell-labs.com"><span class="email">dmk@bell-labs.com</span></a></span></address>
     1274         <address class="vcard"><span class="vcardline"><span class="fn">Lou Montulli</span><span class="n hidden"><span class="family-name">Montulli</span><span class="given-name">Lou</span></span></span><span class="org vcardline">Epinions.com, Inc.</span><span class="adr"><span class="street-address vcardline">2037 Landings Dr.</span><span class="vcardline"><span class="locality">Mountain View</span>, <span class="region">CA</span>&nbsp;<span class="postal-code">94301</span></span></span><span class="vcardline">EMail: <a href="mailto:lou@montulli.org"><span class="email">lou@montulli.org</span></a></span></address>
     1275      </div>
    12981276      <hr class="noprint">
    12991277      <h1 id="rfc.index" class="np"><a href="#rfc.index">Index</a></h1>
     
    13391317         </ul>
    13401318      </div>
     1319      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
     1320      <p>Copyright © The Internet Society (2000). All Rights Reserved.</p>
     1321      <p>This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise
     1322         explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without
     1323         restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative
     1324         works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references
     1325         to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards
     1326         in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to
     1327         translate it into languages other than English.
     1328      </p>
     1329      <p>The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.</p>
     1330      <p>This document and the information contained herein is provided on an “AS IS” basis and THE INTERNET SOCIETY AND THE INTERNET
     1331         ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE
     1332         OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR
     1333         PURPOSE.
     1334      </p>
     1335      <hr class="noprint">
     1336      <h1 class="np"><a id="rfc.ipr" href="#rfc.ipr">Intellectual Property</a></h1>
     1337      <p>The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed
     1338         to pertain to the implementation or use of the technology described in this document or the extent to which any license under
     1339         such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights.
     1340         Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be
     1341         found in BCP-11. Copies of claims of rights made available for publication and any assurances of licenses to be made available,
     1342         or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors
     1343         or users of this specification can be obtained from the IETF Secretariat.
     1344      </p>
     1345      <p>The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary
     1346         rights which may cover technology that may be required to practice this standard. Please address the information to the IETF
     1347         Executive Director.
     1348      </p>
     1349      <h1>Acknowledgment</h1>
     1350      <p>Funding for the RFC Editor function is currently provided by the Internet Society.</p>
    13411351   </body>
    13421352</html>
Note: See TracChangeset for help on using the changeset viewer.