< draft-nottingham-http-browser-hints-00.txt   draft-nottingham-http-browser-hints-01.txt >
Network Working Group M. Nottingham Network Working Group M. Nottingham
Internet-Draft May 17, 2011 Internet-Draft May 27, 2011
Intended status: Informational Intended status: Informational
Expires: November 18, 2011 Expires: November 28, 2011
HTTP Browser Hints HTTP Browser Hints
draft-nottingham-http-browser-hints-00 draft-nottingham-http-browser-hints-01
Abstract Abstract
Over time, Web browsers have adapted how they use HTTP based upon Over time, Web browsers have adapted how they use HTTP based upon
common server configurations and behaviours. While this is necessary common server configurations and behaviours. While this is necessary
in the common case, it can be detrimental for performance and in the common case, it can be detrimental for performance and
interoperability. interoperability.
This document establishes a mechanism whereby origin servers can make This document establishes a mechanism whereby origin servers can make
available hints for browsers about their preferences and available hints for browsers about their preferences and
skipping to change at page 1, line 41 skipping to change at page 1, line 41
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on November 18, 2011. This Internet-Draft will expire on November 28, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 25 skipping to change at page 2, line 25
2. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. A file format for Browser Hints . . . . . . . . . . . . . . . . 3 3. A file format for Browser Hints . . . . . . . . . . . . . . . . 3
4. Discovering Browser Hints for a Web site . . . . . . . . . . . 4 4. Discovering Browser Hints for a Web site . . . . . . . . . . . 4
5. Pre-defined Browser Hints . . . . . . . . . . . . . . . . . . . 4 5. Pre-defined Browser Hints . . . . . . . . . . . . . . . . . . . 4
5.1. max-conns . . . . . . . . . . . . . . . . . . . . . . . . . 4 5.1. max-conns . . . . . . . . . . . . . . . . . . . . . . . . . 4
5.2. pconn-ip . . . . . . . . . . . . . . . . . . . . . . . . . 5 5.2. pconn-ip . . . . . . . . . . . . . . . . . . . . . . . . . 5
5.3. max-pipeline-depth . . . . . . . . . . . . . . . . . . . . 5 5.3. max-pipeline-depth . . . . . . . . . . . . . . . . . . . . 5
5.4. small-hdrs . . . . . . . . . . . . . . . . . . . . . . . . 5 5.4. small-hdrs . . . . . . . . . . . . . . . . . . . . . . . . 5
5.5. no-referer . . . . . . . . . . . . . . . . . . . . . . . . 5 5.5. no-referer . . . . . . . . . . . . . . . . . . . . . . . . 5
5.6. send-ref . . . . . . . . . . . . . . . . . . . . . . . . . 6 5.6. send-ref . . . . . . . . . . . . . . . . . . . . . . . . . 6
5.7. chunk-req-bodies . . . . . . . . . . . . . . . . . . . . . 6
5.8. omit-cookies . . . . . . . . . . . . . . . . . . . . . . . 6
6. The Ref HTTP Request Header . . . . . . . . . . . . . . . . . . 6 6. The Ref HTTP Request Header . . . . . . . . . . . . . . . . . . 6
7. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 7. Security Considerations . . . . . . . . . . . . . . . . . . . . 6
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
8.1. The 'browser-hints' Well-Known URI . . . . . . . . . . . . 6 8.1. The 'browser-hints' Well-Known URI . . . . . . . . . . . . 7
8.2. The HTTP Browser Hints Registry . . . . . . . . . . . . . . 6 8.2. The HTTP Browser Hints Registry . . . . . . . . . . . . . . 7
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7
9.1. Normative References . . . . . . . . . . . . . . . . . . . 7 9.1. Normative References . . . . . . . . . . . . . . . . . . . 7
9.2. Informative References . . . . . . . . . . . . . . . . . . 7 9.2. Informative References . . . . . . . . . . . . . . . . . . 8
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . . 8 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . . 8
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 8 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction 1. Introduction
HTTP [RFC2616] clients -- especially browsers -- typically use HTTP [RFC2616] clients -- especially browsers -- typically use
hardcoded values or heuristics to determine how many TCP connections hardcoded values or heuristics to determine how many TCP connections
to use to a server, based on common-case server behaviours and to use to a server, based on common-case server behaviours and
limitations. limitations.
skipping to change at page 6, line 17 skipping to change at page 6, line 17
5.6. send-ref 5.6. send-ref
o Browser Hint Name: send-ref o Browser Hint Name: send-ref
o Description: When true, this hint indicates that clients can omit o Description: When true, this hint indicates that clients can omit
the Referer HTTP request header when sending requests to the site, the Referer HTTP request header when sending requests to the site,
if they instead send a Ref HTTP request header (see Section 6). if they instead send a Ref HTTP request header (see Section 6).
o Value Type: true | false o Value Type: true | false
o Contact: mnot@mnot.net o Contact: mnot@mnot.net
5.7. chunk-req-bodies
o Browser Hint Name: chunk-req-bodies
o Description: When true, this hint indicates that the server can
successfully process a request with a chunk-encoded body; i.e.,
that it should not return a 411 Length Required status. Note that
clients may still require a 411 response status, even in when this
hint is present. When false, the server may or may not require a
Content-Length on requests with bodies.
o Value Type: true | false
o Contact: mnot@mnot.net
5.8. omit-cookies
o Browser Hint Name: omit-cookies
o Description: This hint contains a list of cookie [RFC6265] cookie-
names which can be omitted in requests sent to this site.
o Value Type: Array of strings
o Contact: mnot@mnot.net
6. The Ref HTTP Request Header 6. The Ref HTTP Request Header
TBD: relative URI referer header TBD: relative URI referer header
7. Security Considerations 7. Security Considerations
TBD TBD
8. IANA Considerations 8. IANA Considerations
8.1. The 'browser-hints' Well-Known URI 8.1. The 'browser-hints' Well-Known URI
This document defines the "browser-hints" Well-Known URI [RFC5785]. This document defines the "browser-hints" Well-Known URI [RFC5785].
o URI suffix: browser-hints o URI suffix: browser-hints
o Change controller: mnot@mnot.net o Change controller: mnot@mnot.net
o Specification document(s): [this document] o Specification document(s): [this document]
o Related information: o Related information:
8.2. The HTTP Browser Hints Registry 8.2. The HTTP Browser Hints Registry
skipping to change at page 8, line 5 skipping to change at page 8, line 25
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008. May 2008.
[RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security
(TLS) Protocol Version 1.2", RFC 5246, August 2008. (TLS) Protocol Version 1.2", RFC 5246, August 2008.
[RFC5785] Nottingham, M. and E. Hammer-Lahav, "Defining Well-Known [RFC5785] Nottingham, M. and E. Hammer-Lahav, "Defining Well-Known
Uniform Resource Identifiers (URIs)", RFC 5785, Uniform Resource Identifiers (URIs)", RFC 5785,
April 2010. April 2010.
[RFC6265] Barth, A., "HTTP State Management Mechanism", RFC 6265,
April 2011.
Appendix A. Acknowledgements Appendix A. Acknowledgements
Thanks to Mike Belshe, Anirban Kundu, Patrick McManus, and Steve Thanks to Mike Belshe, Poul-Henning Kamp, Anirban Kundu, Patrick
Souders for their suggestions and feedback. McManus, and Steve Souders for their suggestions and feedback.
The author takes all responsibility for errors and omissions. The author takes all responsibility for errors and omissions.
Author's Address Author's Address
Mark Nottingham Mark Nottingham
Email: mnot@mnot.net Email: mnot@mnot.net
URI: http://www.mnot.net/ URI: http://www.mnot.net/
 End of changes. 11 change blocks. 
10 lines changed or deleted 34 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/