Specification document(s):
RFC2616 [11]
2.1.105. Header field: Timeout
Applicable protocol: http [11]
Status: standard
Author/change controller:
IETF (iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC2518 [10]
2.1.106. Header field: Trailer
Applicable protocol: http [11]
Status: standard
Author/change controller:
IETF (iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC2616 [11]
2.1.107. Header field: Transfer-Encoding
Applicable protocol: http [11]
Status: standard
Author/change controller:
IETF (iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC2616 [11]
2.1.108. Header field: URI
Applicable protocol: http [11]
Status: standard
Author/change controller:
IETF (iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC2068 [4]
2.1.109. Header field: Upgrade
Applicable protocol: http [11]
Status: standard
Author/change controller:
IETF (iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC2616 [11]
2.1.110. Header field: User-Agent
Applicable protocol: http [11]
Status: standard
Author/change controller:
IETF (iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC2616 [11]
2.1.111. Header field: Variant-Vary
Applicable protocol: http [11]
Status: experimental
Author/change controller:
Andrew H. Mutz (mutz@hpl.hp.com)
Koen Holtman (koen@win.tue.nl)
Specification document(s):
RFC2295 [7]
2.1.112. Header field: Vary
Applicable protocol: http [11]
Status: standard
Author/change controller:
IETF (iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC2616 [11]
2.1.113. Header field: Via
Applicable protocol: http [11]
Status: standard
Author/change controller:
IETF (iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC2616 [11]
2.1.114. Header field: WWW-Authenticate
Applicable protocol: http [11]
Status: standard
Author/change controller:
IETF (iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC2616 [11]
2.1.115. Header field: Want-Digest
Applicable protocol: http [11]
Status: standard
Author/change controller:
IETF (iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC3230 [17]
2.1.116. Header field: Warning
Applicable protocol: http [11]
Status: standard
Author/change controller:
IETF (iesg@ietf.org)
Internet Engineering Task Force
Specification document(s):
RFC2616 [11]
2.2. Provisional HTTP Header Field Submissions
Header name Protocol
----------- --------
Compliance http
Content-Transfer-Encoding http
Cost http
Message-ID http
Non-Compliance http
Optional http
Resolution-Hint http
Resolver-Location http
SubOK http
Subst http
Title http
UA-Color http
UA-Media http
UA-Pixels http
UA-Resolution http
UA-Windowpixels http
Version http
2.2.1. Header field: Compliance
Applicable protocol: http [11]
Status: provisional
Author/change controller: Jeffrey C. Mogul (mogul@wrl.dec.com)
Western Research Laboratory, Digital Equipment Corporation Josh
Cohen (josh@netscape.com) Netscape Communications Corporation
Scott Lawrence (lawrence@agranat.com) Agranat Systems, Inc.
Specification document(s):
OPTIONS messages [31]
2.2.2. Header field: Content-Transfer-Encoding
Applicable protocol: http [11]
Status: provisional
Author/change controller:
Tim Berners-Lee (timbl@w3.org)
MIT Laboratory for Computer Science
Specification document(s):
Object Headers [2]
2.2.3. Header field: Cost
Applicable protocol: http [11]
Status: provisional
Author/change controller:
Tim Berners-Lee (timbl@w3.org)
MIT Laboratory for Computer Science
Specification document(s):
Object Headers [2]
2.2.4. Header field: Message-ID
Applicable protocol: http [11]
Status: provisional
Author/change controller:
Tim Berners-Lee (timbl@w3.org)
MIT Laboratory for Computer Science
Specification document(s):
Object Headers [2]
2.2.5. Header field: Non-Compliance
Applicable protocol: http [11]
Status: provisional
Author/change controller: Jeffrey C. Mogul (mogul@wrl.dec.com)
Western Research Laboratory, Digital Equipment Corporation Josh
Cohen (josh@netscape.com) Netscape Communications Corporation
Scott Lawrence (lawrence@agranat.com) Agranat Systems, Inc.
Specification document(s):
OPTIONS messages [31]
2.2.6. Header field: Optional
Applicable protocol: http [11]
Status: provisional
Author/change controller:
John Mallery (jcma@ai.mit.edu)
MIT Artificial Intelligence Laboratory
Lewis Girod (girod@lcs.mit.edu)
MIT Laboratory for Computer Science
Benjie Chen (benjie@lcs.mit.edu)
MIT Laboratory for Computer Science
Henrik Frystyk Nielsen (frystyk@w3.org)
World Wide Web Consortium
Specification document(s):
WIRE [32]
2.2.7. Header field: Resolution-Hint
Applicable protocol: http [11]
Status: provisional
Author/change controller:
John Mallery (jcma@ai.mit.edu)
MIT Artificial Intelligence Laboratory
Lewis Girod (girod@lcs.mit.edu)
MIT Laboratory for Computer Science
Benjie Chen (benjie@lcs.mit.edu)
MIT Laboratory for Computer Science
Henrik Frystyk Nielsen (frystyk@w3.org)
World Wide Web Consortium
Specification document(s):
WIRE [32]
2.2.8. Header field: Resolver-Location
Applicable protocol: http [11]
Status: provisional
Author/change controller:
John Mallery (jcma@ai.mit.edu)
MIT Artificial Intelligence Laboratory
Lewis Girod (girod@lcs.mit.edu)
MIT Laboratory for Computer Science
Benjie Chen (benjie@lcs.mit.edu)
MIT Laboratory for Computer Science
Henrik Frystyk Nielsen (frystyk@w3.org)
World Wide Web Consortium
Specification document(s):
WIRE [32]
2.2.9. Header field: SubOK
Applicable protocol: http [11]
Status: provisional
Author/change controller: Jeffrey C. Mogul (mogul@wrl.dec.com)
Western Research Laboratory, Digital Equipment Corporation Arthur
van Hoff (avh@marimba.com) Marimba, Inc.
Specification document(s):
Duplicate Suppression [33]
2.2.10. Header field: Subst
Applicable protocol: http [11]
Status: provisional
Author/change controller: Jeffrey C. Mogul (mogul@wrl.dec.com)
Western Research Laboratory, Digital Equipment Corporation Arthur
van Hoff (avh@marimba.com) Marimba, Inc.
Specification document(s):
Duplicate Suppression [33]
2.2.11. Header field: Title
Applicable protocol: http [11]
Status: provisional
Author/change controller:
Tim Berners-Lee (timbl@w3.org)
MIT Laboratory for Computer Science
Specification document(s):
Object Headers [2]
2.2.12. Header field: UA-Color
Applicable protocol: http [11]
Status: provisional
Author/change controller:
Larry Masinter (LMM@acm.org)
Adobe Systems
Lou Montulli (montulli@netscape.com)
Netscape Communications Corp.
Andrew H. Mutz (mutz@hpl.hp.com)
Hewlett-Packard Company
Specification document(s):
UA Attributes [30]
2.2.13. Header field: UA-Media
Applicable protocol: http [11]
Status: provisional
Author/change controller:
Larry Masinter (LMM@acm.org)
Adobe Systems
Lou Montulli (montulli@netscape.com)
Netscape Communications Corp.
Andrew H. Mutz (mutz@hpl.hp.com)
Hewlett-Packard Company
Specification document(s):
UA Attributes [30]
2.2.14. Header field: UA-Pixels
Applicable protocol: http [11]
Status: provisional
Author/change controller:
Larry Masinter (LMM@acm.org)
Adobe Systems
Lou Montulli (montulli@netscape.com)
Netscape Communications Corp.
Andrew H. Mutz (mutz@hpl.hp.com)
Hewlett-Packard Company
Specification document(s):
UA Attributes [31]
2.2.15. Header field: UA-Resolution
Applicable protocol: http [11]
Status: provisional
Author/change controller:
Larry Masinter (LMM@acm.org)
Adobe Systems
Lou Montulli (montulli@netscape.com)
Netscape Communications Corp.
Andrew H. Mutz (mutz@hpl.hp.com)
Hewlett-Packard Company
Specification document(s):
UA Attributes [30]
2.2.16. Header field: UA-Windowpixels
Applicable protocol: http [11]
Status: provisional
Author/change controller:
Larry Masinter (LMM@acm.org)
Adobe Systems
Lou Montulli (montulli@netscape.com)
Netscape Communications Corp.
Andrew H. Mutz (mutz@hpl.hp.com)
Hewlett-Packard Company
Specification document(s):
UA Attributes [30]
2.2.17. Header field: Version
Applicable protocol: http [11]
Status: provisional
Author/change controller:
Tim Berners-Lee (timbl@w3.org)
MIT Laboratory for Computer Science
Specification document(s):
Object Headers [2]
3. IANA Considerations
This specification provides initial registrations of HTTP header
fields in the "Permanent Message Header Field Registry", defined by
Registration Procedures for Message Header Fields [1].
It also provides initial submissions of HTTP header fields in the
"Provisional Message Header Field Repository", defined by the same
document.
4. Security Considerations
No security considerations are introduced by this document beyond
those already inherent in use of the HTTP header fields referenced.
5. Acknowledgements
The authors would like to thank Graham Klyne for his work in defining
the message header registries, his input and help in preparing this
document, and the registry generation software.
6. Informative References
[1] Klyne, G., Nottingham, M., and J. Mogul, "Registration
Procedures for Message Header Fields", BCP 90, RFC 3864,
September 2004.
[2] Berners-Lee, T., "Object Header lines in HTTP", May 1994,
<http://www.w3.org/Protocols/HTTP/Object_Headers.html>.
[3] Berners-Lee, T., Fielding, R., and H. Nielsen, "Hypertext
Transfer Protocol -- HTTP/1.0", RFC 1945, May 1996.
[4] Fielding, R., Gettys, J., Mogul, J., Nielsen, H., and T.
Berners-Lee, "Hypertext Transfer Protocol -- HTTP/1.1", RFC
2068, January 1997.
[5] Kristol, D. and L. Montulli, "HTTP State Management Mechanism",
RFC 2109, February 1997.
[6] Mogul, J. and P. Leach, "Simple Hit-Metering and Usage-Limiting
for HTTP", RFC 2227, October 1997.
[7] Holtman, K. and A. Mutz, "Transparent Content Negotiation in
HTTP", RFC 2295, March 1998.
[8] Holtman, K., "The Safe Response Header Field", RFC 2310, April
1998.
[9] Masinter, L., "Hyper Text Coffee Pot Control Protocol
(HTCPCP/1.0)", RFC 2324, April 1998.
[10] Goland, Y., Whitehead, E., Faizi, A., Carter, S., and D.
Jensen, "HTTP Extensions for Distributed Authoring -- WEBDAV",
RFC 2518, February 1999.
[11] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L.,
Leach, P., and T. Berners-Lee, "Hypertext Transfer Protocol --
HTTP/1.1", RFC 2616, June 1999.
[12] Franks, J., Hallam-Baker, P., Hostetler, J., Lawrence, S.,
Leach, P., Luotonen, A., and L. Stewart, "HTTP Authentication:
Basic and Digest Access Authentication", RFC 2617, June 1999.
[13] Rescorla, E. and A. Schiffman, "The Secure HyperText Transfer
Protocol", RFC 2660, August 1999.
[14] Nielsen, H., Leach, P., and S. Lawrence, "An HTTP Extension
Framework", RFC 2774, February 2000.
[15] Kristol, D. and L. Montulli, "HTTP State Management Mechanism",
RFC 2965, October 2000.
[16] Mogul, J., Krishnamurthy, B., Douglis, F., Feldmann, A.,
Goland, Y., van Hoff, A., and D. Hellerstein, "Delta encoding
in HTTP", RFC 3229, January 2002.
[17] Mogul, J. and A. Van Hoff, "Instance Digests in HTTP", RFC
3230, January 2002.
[18] Clemm, G., Amsden, J., Ellison, T., Kaler, C., and J.
Whitehead, "Versioning Extensions to WebDAV (Web Distributed
Authoring and Versioning)", RFC 3253, March 2002.
[19] Whitehead, J. and J. Reschke, Ed., "Web Distributed Authoring
and Versioning (WebDAV) Ordered Collections Protocol", RFC
3648, December 2003.
[20] Hoff, A., Payne, J., Hapner, M., Carter, S., and M. Medin, "The
HTTP Distribution and Replication Protocol", W3C NOTE NOTE-
drp-19970825, August 1997.
[21] Raggett, D., Hors, A., and I. Jacobs, "HTML 4.01
Specification", W3C REC REC-html401-19991224, December 1999.
[22] Hensley, P., Metral, M., Shardanand, U., Converse, D., and M.
Myers, "Implementation of OPS Over HTTP", W3C NOTE NOTE-OPS-
OverHTTP, June 1997.
[23] Marchiori, M., "The Platform for Privacy Preferences 1.0
(P3P1.0) Specification", W3C REC REC-P3P-20020416, April 2002.
[24] Krauskopf, T., Miller, J., Resnick, P., and W. Treese, "PICS
1.1 Label Distribution -- Label Syntax and Communication
Protocols", W3C REC REC-PICS-labels-961031, October 1996.
[25] Nottingham, M. and X. Liu, "Edge Architecture Specification",
W3C NOTE NOTE-edge-arch-20010804, August 2001.
[26] Chung, E. and D. Dardailler, "White Paper: Joint Electronic
Payment Initiative", W3C NOTE NOTE-jepi-970519, May 1997.
[27] Hallam-Baker, P., "Notification for Proxy Caches", W3C NOTE WD-
proxy-960221, February 1996.
[28] Box, D., Ehnebuske, D., Kakivaya, G., Layman, A., Mendelsohn,
N., Nielsen, H., Thatte, S., and D. Winer, "Simple Object
Access Protocol (SOAP) 1.1", W3C NOTE NOTE-SOAP-20000508, May
2000.
[29] Connolly, D., Prod’hommeaux, E., Nielsen, H., and R. Khare,
"PEP Specification: an Extension Mechanism for HTTP", Nov 1998,
<http://www.w3.org/TR/WD-http-pep>.
[30] Masinter, L., Montulli, L., and A. Mutz, "User-Agent Display
Attributes Headers", Work in Progress, November 1996.
[31] Mogul, J., Cohen, J., and S. Lawrence, "Specification of
HTTP/1.1 OPTIONS messages", Work in Progress, August 1997.
[32] Girod, L., Chen, B., Henrik, H., and J. Mallery, "WIRE - W3
Identifier Resolution Extensions", Work in Progress, March
1998.
[33] Mogul, J. and A. van Hoff, "Duplicate Suppression in HTTP",
Work in Progress, April 1998.
Authors’ Addresses
Mark Nottingham
EMail: mnot@pobox.com
URI: http://www.mnot.net/
Jeffrey C. Mogul
HP Labs
1501 Page Mill Road
Palo Alto, CA 94304
US
EMail: JeffMogul@acm.org
Full Copyright Statement
Copyright (C) The Internet Society (2005).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM 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.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf-
ipr@ietf.org.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.