php-faq.com logo March 10, 2010, 3:28 pm 
 
  This is the unoffical php FAQ. The official php FAQ can be found at http://www.php.net/faq
  faq    Books    McCormick Spices    Links    Suggest    About    Old Bay Seasoning    Privacy    Terms   

17 References - RFC2616 (HTTP/1.1. Draft June 1999)

RFC2616 HTTP/1.1 Draft (1999)
Chapter 1 - Introduction
Chapter 2 - Notational Conventions
Chapter 3 - Protocol Parameters
Chapter 4 - HTTP Messages
Chapter 5 - HTTP Request
Chapter 6 - Response
Chapter 7 - Entity
Chapter 8 - Connections
Chapter 9 - Methods
Chapter 10 - Status Code Definitions
Chapter 11 - Access Authentication
Chapter 12 - Content Negotiation
Chapter 13 - Caching in HTTP
Chapter 14 - Header Field Definitions
Chapter 15 - Security Considerations
Chapter 16 - Acknowledgements
Chapter 17 - References
Chapter 18 - Authors Addresses
Chapter 19 - Appendices
 17 References 

     [1] Alvestrand, H., "Tags for the Identification of Languages",
         RFC 1766, March 1995.
  
     [2] Anklesaria, F., McCahill, M., Lindner, P., Johnson, D., Torrey,
         D. and B. Alberti, "The Internet Gopher Protocol (a distributed
         document search and retrieval protocol)", RFC 1436, March 1993.
  
     [3] Berners-Lee, T., "Universal Resource Identifiers in WWW", 
         RFC 1630, June 1994.
  
     [4] Berners-Lee, T., Masinter, L. and M. McCahill, "Uniform Resource
         Locators (URL)", RFC 1738, December 1994.
  
     [5] Berners-Lee, T. and D. Connolly, "Hypertext Markup Language -
         2.0", RFC 1866, November 1995.
  
     [6] Berners-Lee, T., Fielding, R. and H. Frystyk, "Hypertext Transfer
         Protocol -- HTTP/1.0", RFC 1945, May 1996.
  
     [7] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
         Extensions (MIME) Part One: Format of Internet Message Bodies",
         RFC 2045, November 1996.
  
     [8] Braden, R., "Requirements for Internet Hosts -- Communication
         Layers", STD 3, RFC 1123, October 1989.
  
     [9] Crocker, D., "Standard for The Format of ARPA Internet Text
         Messages", STD 11, RFC 822, August 1982.
  
     [10] Davis, F., Kahle, B., Morris, H., Salem, J., Shen, T., Wang, R.,
          Sui, J., and M. Grinbaum, "WAIS Interface Protocol Prototype
          Functional Specification," (v1.5), Thinking Machines
          Corporation, April 1990.
  
     [11] Fielding, R., "Relative Uniform Resource Locators", RFC 1808,
          June 1995.
  
     [12] Horton, M. and R. Adams, "Standard for Interchange of USENET
          Messages", RFC 1036, December 1987.
  
     [13] Kantor, B. and P. Lapsley, "Network News Transfer Protocol",
          RFC 977, February 1986.
  
     [14] Moore, K., "MIME (Multipurpose Internet Mail Extensions) Part
          Three: Message Header Extensions for Non-ASCII Text", RFC 2047,
          November 1996.
  
     [15] Nebel, E. and L. Masinter, "Form-based File Upload in HTML",
          RFC 1867, November 1995.
  
     [16] Postel, J., "Simple Mail Transfer Protocol", STD 10, RFC 821,
          August 1982.
  
     [17] Postel, J., "Media Type Registration Procedure", RFC 1590,
          November 1996.
  
     [18] Postel, J. and J. Reynolds, "File Transfer Protocol", STD 9,
          RFC 959, October 1985.
  
     [19] Reynolds, J. and J. Postel, "Assigned Numbers", STD 2, RFC 1700,
          October 1994.
  
     [20] Sollins, K. and L. Masinter, "Functional Requirements for
          Uniform Resource Names", RFC 1737, December 1994.
  
     [21] US-ASCII. Coded Character Set - 7-Bit American Standard Code for
          Information Interchange. Standard ANSI X3.4-1986, ANSI, 1986.
  
     [22] 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.
  
     [23] Meyers, J. and M. Rose, "The Content-MD5 Header Field",
          RFC 1864, October 1995.
  
     [24] Carpenter, B. and Y. Rekhter, "Renumbering Needs Work",
          RFC 1900, February 1996.
  
     [25] Deutsch, P., "GZIP file format specification version 4.3",
          RFC 1952, May 1996.
  
     [26] Venkata N. Padmanabhan, and Jeffrey C. Mogul. "Improving HTTP
          Latency", 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/.
  
     [27] Joe Touch, John Heidemann, and Katia Obraczka. "Analysis of HTTP
          Performance", ,
          ISI Research Report ISI/RR-98-463, (original report dated Aug.
          1996), USC/Information Sciences Institute, August 1998.
  
     [28] Mills, D., "Network Time Protocol (Version 3) Specification,
          Implementation and Analysis", RFC 1305, March 1992.
  
     [29] Deutsch, P., "DEFLATE Compressed Data Format Specification
          version 1.3", RFC 1951, May 1996.
  
     [30] S. Spero, "Analysis of HTTP Performance Problems,"
          http://sunsite.unc.edu/mdma-release/http-prob.html.
  
     [31] Deutsch, P. and J. Gailly, "ZLIB Compressed Data Format
          Specification version 3.3", RFC 1950, May 1996.
  
     [32] Franks, J., Hallam-Baker, P., Hostetler, J., Leach, P.,
          Luotonen, A., Sink, E. and L. Stewart, "An Extension to HTTP:
          Digest Access Authentication", RFC 2069, January 1997.
  
     [33] Fielding, R., Gettys, J., Mogul, J., Frystyk, H. and T.
          Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1",
          RFC 2068, January 1997.
  
     [34] Bradner, S., "Key words for use in RFCs to Indicate Requirement
          Levels", BCP 14, RFC 2119, March 1997.
  
     [35] Troost, R. and Dorner, S., "Communicating Presentation
          Information in Internet Messages: The Content-Disposition
          Header", RFC 1806, June 1995.
  
     [36] Mogul, J., Fielding, R., Gettys, J. and H. Frystyk, "Use and
          Interpretation of HTTP Version Numbers", RFC 2145, May 1997.
          [jg639]
  
     [37] Palme, J., "Common Internet Message Headers", RFC 2076, February
          1997. [jg640]
  
     [38] Yergeau, F., "UTF-8, a transformation format of Unicode and
          ISO-10646", RFC 2279, January 1998. [jg641]
  
     [39] Nielsen, H.F., Gettys, J., Baird-Smith, A., Prud'hommeaux, E.,
          Lie, H., and C. Lilley. 
          "Network Performance Effects of HTTP/1.1, CSS1, and PNG," 
          Proceedings of ACM SIGCOMM '97, Cannes France, September 1997.[jg642]
  
     [40] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
          Extensions (MIME) Part Two: Media Types", RFC 2046, November
          1996. [jg643]
  
     [41] Alvestrand, H., "IETF Policy on Character Sets and Languages",
          BCP 18, RFC 2277, January 1998. [jg644]
  
     [42] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform Resource
          Identifiers (URI): Generic Syntax and Semantics", RFC 2396,
          August 1998. [jg645]
  
     [43] Franks, J., Hallam-Baker, P., Hostetler, J., Lawrence, S.,
          Leach, P., Luotonen, A., Sink, E. and L. Stewart, "HTTP
          Authentication: Basic and Digest Access Authentication",
          RFC 2617, June 1999. [jg646]
  
     [44] Luotonen, A., 
          "Tunneling TCP based protocols through Web proxy servers," 
          Work in Progress. [jg647]
  
     [45] Palme, J. and A. Hopmann, "MIME E-mail Encapsulation of
          Aggregate Documents, such as HTML (MHTML)", RFC 2110, March
          1997.
  
     [46] Bradner, S., "The Internet Standards Process -- Revision 3", BCP
          9, RFC 2026, October 1996.
  
     [47] Masinter, L., "Hyper Text Coffee Pot Control Protocol
          (HTCPCP/1.0)", RFC 2324, 1 April 1998.
  
     [48] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
          Extensions (MIME) Part Five: Conformance Criteria and Examples",
          RFC 2049, November 1996.
  
     [49] Troost, R., Dorner, S. and K. Moore, "Communicating Presentation
          Information in Internet Messages: The Content-Disposition Header
          Field", RFC 2183, August 1997.

Top

Formatted into html by www.php-faq.com

Copyright © The Internet Society (1999). All Rights Reserved.

This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.

The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.

This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Wordpress Theme | Creative Electronics | Find jobs | Find jobs | Computer Jobs