datatracker.ietf.org
Sign in
Version 5.4.0, 2014-04-22
Report a bug

Prefer Header for HTTP
draft-snell-http-prefer-18

Document type: Active Internet-Draft (individual in app area)
Document stream: IETF
Last updated: 2013-01-22 (latest revision 2013-01-07)
Intended RFC status: Proposed Standard
Other versions: plain text, xml, pdf, html

IETF State: (None)
Consensus: Unknown
Document shepherd: No shepherd assigned

IESG State: RFC Ed Queue
RFC Editor State: RFC-EDITOR
Responsible AD: Barry Leiba
IESG Note: Mark Nottingham is the document shepherd.
Send notices to: jasnell@gmail.com, mnot@mnot.net, draft-snell-http-prefer@tools.ietf.org

Network Working Group                                           J. Snell
Internet-Draft                                           January 7, 2013
Intended status: Standards Track
Expires: July 11, 2013

                         Prefer Header for HTTP
                       draft-snell-http-prefer-18

Abstract

   This specification defines an HTTP header field that can be used by a
   client to request that certain behaviors be employed by a server
   while processing a request.

Status of this Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on July 11, 2013.

Copyright Notice

   Copyright (c) 2013 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Snell                     Expires July 11, 2013                 [Page 1]
Internet-Draft                 HTTP Prefer                  January 2013

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1.  Syntax Notation  . . . . . . . . . . . . . . . . . . . . .  4
   2.  The Prefer Request Header Field  . . . . . . . . . . . . . . .  4
     2.1.  Examples . . . . . . . . . . . . . . . . . . . . . . . . .  6
   3.  The Preference-Applied Response Header Field . . . . . . . . .  7
   4.  Preference Definitions . . . . . . . . . . . . . . . . . . . .  8
     4.1.  The "respond-async" Preference . . . . . . . . . . . . . .  8
     4.2.  The "return=representation" and "return=minimal"
           Preferences  . . . . . . . . . . . . . . . . . . . . . . .  9
     4.3.  The "wait" Preference  . . . . . . . . . . . . . . . . . . 11
     4.4.  The "handling=strict" and "handling=lenient"
           Processing Preferences . . . . . . . . . . . . . . . . . . 12
   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 13
     5.1.  The Registry of Preferences  . . . . . . . . . . . . . . . 13
     5.2.  Initial Registry Contents  . . . . . . . . . . . . . . . . 14
   6.  Security Considerations  . . . . . . . . . . . . . . . . . . . 15
   7.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
     7.1.  Normative References . . . . . . . . . . . . . . . . . . . 15
     7.2.  Informative References . . . . . . . . . . . . . . . . . . 16
   Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 16

Snell                     Expires July 11, 2013                 [Page 2]
Internet-Draft                 HTTP Prefer                  January 2013

1.  Introduction

   Within the course of processing an HTTP request there are typically a
   range of required and optional behaviors that a server or
   intermediary can employ.  These often manifest in a variety of subtle
   and not-so-subtle ways within the response.

   For example, when using the HTTP PUT method to modify a resource --
   similar to that defined for the Atom Publishing Protocol [RFC5023] --
   the server is given the option of returning either a complete
   representation of a modified resource or a minimal response that
   indicates only the successful completion of the operation.  The
   selection of which type of response to return to the client generally
   has no bearing on the successful processing of the request but could,
   for instance, have an impact on what actions the client must take
   after receiving the response.  That is, returning a representation of
   the modified resource within the response can allow the client to
   avoid sending an additional subsequent GET request.

   Similarly, servers that process requests are often faced with

[include full document text]