rfc2616-sec17.html 11.5 KB

Raw Blame History Permalink

<!DOCTYPE html
     PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
     "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns='http://www.w3.org/1999/xhtml'>
<head><title>HTTP/1.1: References</title></head>
<body><address>part of <a rev='Section' href='rfc2616.html'>Hypertext Transfer Protocol -- HTTP/1.1</a><br />
RFC 2616 Fielding, et al.</address>
<h2><a id='sec17'>17</a> References</h2>
<dl class='bib'>
<dt><a id='bib1'>[1]</a></dt>
<dd>Alvestrand, H.,  <cite><a href='http://www.ietf.org/rfc/rfc1766.txt'>Tags for the Identification of Languages</a></cite> , RFC 1766, March 1995. </dd>
<dt><a id='bib2'>[2]</a></dt>
<dd>Anklesaria, F., McCahill, M., Lindner, P., Johnson, D., Torrey, D. and B. Alberti,  <cite><a href='http://www.ietf.org/rfc/rfc1436.txt'>The Internet Gopher Protocol (a distributed document search and retrieval protocol)</a></cite> , RFC 1436, March 1993. </dd>
<dt><a id='bib3'>[3]</a></dt>
<dd>Berners-Lee, T.,  <cite><a href='http://www.ietf.org/rfc/rfc1630.txt'>Universal Resource Identifiers in WWW</a></cite> , RFC 1630, June 1994. </dd>
<dt><a id='bib4'>[4]</a></dt>
<dd>Berners-Lee, T., Masinter, L. and M. McCahill,  <cite><a href='http://www.ietf.org/rfc/rfc1738.txt'>Uniform Resource Locators (URL)</a></cite> , RFC 1738, December 1994. </dd>
<dt><a id='bib5'>[5]</a></dt>
<dd>Berners-Lee, T. and D. Connolly,  <cite><a href='http://www.ietf.org/rfc/rfc1866.txt'>Hypertext Markup Language - 2.0</a></cite> , RFC 1866, November 1995. </dd>
<dt><a id='bib6'>[6]</a></dt>
<dd>Berners-Lee, T., Fielding, R. and H. Frystyk,  <cite><a href='http://www.ietf.org/rfc/rfc1945.txt'>Hypertext Transfer Protocol -- HTTP/1.0</a></cite> , RFC 1945, May 1996. </dd>
<dt><a id='bib7'>[7]</a></dt>
<dd>Freed, N. and N. Borenstein,  <cite><a href='http://www.ietf.org/rfc/rfc2045.txt'>Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</a></cite> , RFC 2045, November 1996. </dd>
<dt><a id='bib8'>[8]</a></dt>
<dd>Braden, R.,  <cite><a href='http://www.ietf.org/rfc/rfc1123.txt'>Requirements for Internet Hosts -- Communication Layers</a></cite> , STD 3, RFC 1123, October 1989. </dd>
<dt><a id='bib9'>[9]</a></dt>
<dd>Crocker, D.,  <cite><a href='http://www.ietf.org/rfc/rfc0822.txt'>Standard for The Format of ARPA Internet Text Messages</a></cite> , STD 11, RFC 822, August 1982. </dd>
<dt><a id='bib10'>[10]</a></dt>
<dd>Davis, F., Kahle, B., Morris, H., Salem, J., Shen, T., Wang, R., Sui, J., and M. Grinbaum,  <cite>WAIS Interface Protocol Prototype Functional Specification,</cite>  (v1.5), Thinking Machines Corporation, April 1990. </dd>
<dt><a id='bib11'>[11]</a></dt>
<dd>Fielding, R.,  <cite><a href='http://www.ietf.org/rfc/rfc1808.txt'>Relative Uniform Resource Locators</a></cite> , RFC 1808, June 1995. </dd>
<dt><a id='bib12'>[12]</a></dt>
<dd>Horton, M. and R. Adams,  <cite><a href='http://www.ietf.org/rfc/rfc1036.txt'>Standard for Interchange of USENET Messages</a></cite> , RFC 1036, December 1987. </dd>
<dt><a id='bib13'>[13]</a></dt>
<dd>Kantor, B. and P. Lapsley,  <cite><a href='http://www.ietf.org/rfc/rfc0977.txt'>Network News Transfer Protocol</a></cite> , RFC 977, February 1986. </dd>
<dt><a id='bib14'>[14]</a></dt>
<dd>Moore, K.,  <cite><a href='http://www.ietf.org/rfc/rfc2047.txt'>MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text</a></cite> , RFC 2047, November 1996. </dd>
<dt><a id='bib15'>[15]</a></dt>
<dd>Nebel, E. and L. Masinter,  <cite><a href='http://www.ietf.org/rfc/rfc1867.txt'>Form-based File Upload in HTML</a></cite> , RFC 1867, November 1995. </dd>
<dt><a id='bib16'>[16]</a></dt>
<dd>Postel, J.,  <cite><a href='http://www.ietf.org/rfc/rfc0821.txt'>Simple Mail Transfer Protocol</a></cite> , STD 10, RFC 821, August 1982. </dd>
<dt><a id='bib17'>[17]</a></dt>
<dd>Postel, J.,  <cite><a href='http://www.ietf.org/rfc/rfc1590.txt'>Media Type Registration Procedure</a></cite> , RFC 1590, November 1996. </dd>
<dt><a id='bib18'>[18]</a></dt>
<dd>Postel, J. and J. Reynolds,  <cite><a href='http://www.ietf.org/rfc/rfc0959.txt'>File Transfer Protocol</a></cite> , STD 9, RFC 959, October 1985. </dd>
<dt><a id='bib19'>[19]</a></dt>
<dd>Reynolds, J. and J. Postel,  <cite><a href='http://www.ietf.org/rfc/rfc1700.txt'>Assigned Numbers</a></cite> , STD 2, RFC 1700, October 1994. </dd>
<dt><a id='bib20'>[20]</a></dt>
<dd>Sollins, K. and L. Masinter,  <cite><a href='http://www.ietf.org/rfc/rfc1737.txt'>Functional Requirements for Uniform Resource Names</a></cite> , RFC 1737, December 1994. </dd>
<dt><a id='bib21'>[21]</a></dt>
<dd> <cite></cite> US-ASCII. Coded Character Set - 7-Bit American Standard Code for Information Interchange. Standard ANSI X3.4-1986, ANSI, 1986. </dd>
<dt><a id='bib22'>[22]</a></dt>
<dd> <cite></cite> ISO-8859. International Standard -- Information Processing -- 8-bit Single-Byte Coded Graphic Character Sets -- Part 1: Latin alphabet No. 1, ISO-8859-1:1987. Part 2: Latin alphabet No. 2, ISO-8859-2, 1987. Part 3: Latin alphabet No. 3, ISO-8859-3, 1988. Part 4: Latin alphabet No. 4, ISO-8859-4, 1988. Part 5: Latin/Cyrillic alphabet, ISO-8859-5, 1988. Part 6: Latin/Arabic alphabet, ISO-8859-6, 1987. Part 7: Latin/Greek alphabet, ISO-8859-7, 1987. Part 8: Latin/Hebrew alphabet, ISO-8859-8, 1988. Part 9: Latin alphabet No. 5, ISO-8859-9, 1990. </dd>
<dt><a id='bib23'>[23]</a></dt>
<dd>Meyers, J. and M. Rose,  <cite><a href='http://www.ietf.org/rfc/rfc1864.txt'>The Content-MD5 Header Field</a></cite> , RFC 1864, October 1995. </dd>
<dt><a id='bib24'>[24]</a></dt>
<dd>Carpenter, B. and Y. Rekhter,  <cite><a href='http://www.ietf.org/rfc/rfc1900.txt'>Renumbering Needs Work</a></cite> , RFC 1900, February 1996. </dd>
<dt><a id='bib25'>[25]</a></dt>
<dd>Deutsch, P.,  <cite><a href='http://www.ietf.org/rfc/rfc1952.txt'>GZIP file format specification version 4.3</a></cite> , RFC 1952, May 1996. </dd>
<dt><a id='bib26'>[26]</a></dt>
<dd>Venkata N. Padmanabhan, and Jeffrey C. Mogul.  <cite><a href='http://www.ncsa.uiuc.edu/SDG/IT94/Proceedings/DDay/mogul/HTTPLatency.html'>Improving HTTP Latency</a></cite> , Computer Networks and ISDN Systems, v. 28, pp. 25-35, Dec. 1995. Slightly revised version of paper in Proc. 2nd International WWW Conference '94: Mosaic and the Web, Oct. 1994, which is available at http://www.ncsa.uiuc.edu/SDG/IT94/Proceedings/DDay/mogul/HTTPLatency.html. </dd>
<dt><a id='bib27'>[27]</a></dt>
<dd>Joe Touch, John Heidemann, and Katia Obraczka.  <cite><a href='http://www.isi.edu/touch/pubs/http-perf96/'>Analysis of HTTP Performance</a></cite> , &lt;URL: http://www.isi.edu/touch/pubs/http-perf96/>, ISI Research Report ISI/RR-98-463, (original report dated Aug. 1996), USC/Information Sciences Institute, August 1998. </dd>
<dt><a id='bib28'>[28]</a></dt>
<dd>Mills, D.,  <cite><a href='http://www.ietf.org/rfc/rfc1305.txt'>Network Time Protocol (Version 3) Specification, Implementation and Analysis</a></cite> , RFC 1305, March 1992. </dd>
<dt><a id='bib29'>[29]</a></dt>
<dd>Deutsch, P.,  <cite><a href='http://www.ietf.org/rfc/rfc1951.txt'>DEFLATE Compressed Data Format Specification version 1.3</a></cite> , RFC 1951, May 1996. </dd>
<dt><a id='bib30'>[30]</a></dt>
<dd>S. Spero,  <cite><a href='http://sunsite.unc.edu/mdma-release/http-prob.html'>Analysis of HTTP Performance Problems,</a></cite>  http://sunsite.unc.edu/mdma-release/http-prob.html. </dd>
<dt><a id='bib31'>[31]</a></dt>
<dd>Deutsch, P. and J. Gailly,  <cite><a href='http://www.ietf.org/rfc/rfc1950.txt'>ZLIB Compressed Data Format Specification version 3.3</a></cite> , RFC 1950, May 1996. </dd>
<dt><a id='bib32'>[32]</a></dt>
<dd>Franks, J., Hallam-Baker, P., Hostetler, J., Leach, P., Luotonen, A., Sink, E. and L. Stewart,  <cite><a href='http://www.ietf.org/rfc/rfc2069.txt'>An Extension to HTTP: Digest Access Authentication</a></cite> , RFC 2069, January 1997. </dd>
<dt><a id='bib33'>[33]</a></dt>
<dd>Fielding, R., Gettys, J., Mogul, J., Frystyk, H. and T. Berners-Lee,  <cite><a href='http://www.ietf.org/rfc/rfc2068.txt'>Hypertext Transfer Protocol -- HTTP/1.1</a></cite> , RFC 2068, January 1997. </dd>
<dt><a id='bib34'>[34]</a></dt>
<dd>Bradner, S.,  <cite><a href='http://www.ietf.org/rfc/rfc2119.txt'>Key words for use in RFCs to Indicate Requirement Levels</a></cite> , BCP 14, RFC 2119, March 1997. </dd>
<dt><a id='bib35'>[35]</a></dt>
<dd>Troost, R. and Dorner, S.,  <cite><a href='http://www.ietf.org/rfc/rfc1806.txt'>Communicating Presentation Information in Internet Messages: The Content-Disposition Header</a></cite> , RFC 1806, June 1995. </dd>
<dt><a id='bib36'>[36]</a></dt>
<dd>Mogul, J., Fielding, R., Gettys, J. and H. Frystyk,  <cite><a href='http://www.ietf.org/rfc/rfc2145.txt'>Use and Interpretation of HTTP Version Numbers</a></cite> , RFC 2145, May 1997. [jg639] </dd>
<dt><a id='bib37'>[37]</a></dt>
<dd>Palme, J.,  <cite><a href='http://www.ietf.org/rfc/rfc2076.txt'>Common Internet Message Headers</a></cite> , RFC 2076, February 1997. [jg640] </dd>
<dt><a id='bib38'>[38]</a></dt>
<dd>Yergeau, F.,  <cite><a href='http://www.ietf.org/rfc/rfc2279.txt'>UTF-8, a transformation format of Unicode and ISO-10646</a></cite> , RFC 2279, January 1998. [jg641] </dd>
<dt><a id='bib39'>[39]</a></dt>
<dd>Nielsen, H.F., Gettys, J., Baird-Smith, A., Prud'hommeaux, E., Lie, H., and C. Lilley.  <cite>Network Performance Effects of HTTP/1.1, CSS1, and PNG,</cite>  Proceedings of ACM SIGCOMM '97, Cannes France, September 1997.[jg642] </dd>
<dt><a id='bib40'>[40]</a></dt>
<dd>Freed, N. and N. Borenstein,  <cite><a href='http://www.ietf.org/rfc/rfc2046.txt'>Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types</a></cite> , RFC 2046, November 1996. [jg643] </dd>
<dt><a id='bib41'>[41]</a></dt>
<dd>Alvestrand, H.,  <cite><a href='http://www.ietf.org/rfc/rfc2277.txt'>IETF Policy on Character Sets and Languages</a></cite> , BCP 18, RFC 2277, January 1998. [jg644] </dd>
<dt><a id='bib42'>[42]</a></dt>
<dd>Berners-Lee, T., Fielding, R. and L. Masinter,  <cite><a href='http://www.ietf.org/rfc/rfc2396.txt'>Uniform Resource Identifiers (URI): Generic Syntax and Semantics</a></cite> , RFC 2396, August 1998. [jg645] </dd>
<dt><a id='bib43'>[43]</a></dt>
<dd>Franks, J., Hallam-Baker, P., Hostetler, J., Lawrence, S., Leach, P., Luotonen, A., Sink, E. and L. Stewart,  <cite><a href='http://www.ietf.org/rfc/rfc2617.txt'>HTTP Authentication: Basic and Digest Access Authentication</a></cite> , RFC 2617, June 1999. [jg646] </dd>
<dt><a id='bib44'>[44]</a></dt>
<dd>Luotonen, A.,  <cite>Tunneling TCP based protocols through Web proxy servers,</cite>  Work in Progress. [jg647] </dd>
<dt><a id='bib45'>[45]</a></dt>
<dd>Palme, J. and A. Hopmann,  <cite><a href='http://www.ietf.org/rfc/rfc2110.txt'>MIME E-mail Encapsulation of Aggregate Documents, such as HTML (MHTML)</a></cite> , RFC 2110, March 1997. </dd>
<dt><a id='bib46'>[46]</a></dt>
<dd>Bradner, S.,  <cite><a href='http://www.ietf.org/rfc/rfc2026.txt'>The Internet Standards Process -- Revision 3</a></cite> , BCP 9, RFC 2026, October 1996. </dd>
<dt><a id='bib47'>[47]</a></dt>
<dd>Masinter, L.,  <cite><a href='http://www.ietf.org/rfc/rfc2324.txt'>Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0)</a></cite> , RFC 2324, 1 April 1998. </dd>
<dt><a id='bib48'>[48]</a></dt>
<dd>Freed, N. and N. Borenstein,  <cite><a href='http://www.ietf.org/rfc/rfc2049.txt'>Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples</a></cite> , RFC 2049, November 1996. </dd>
<dt><a id='bib49'>[49]</a></dt>
<dd>Troost, R., Dorner, S. and K. Moore,  <cite><a href='http://www.ietf.org/rfc/rfc2183.txt'>Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field</a></cite> , RFC 2183, August 1997. </dd>
</dl>
</body></html>