The Accept-Post HTTP Header
draft-wilde-accept-post-02

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2014-02-06
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                            J. Arwe
Internet-Draft                                               S. Speicher
Intended status: Standards Track                                     IBM
Expires: August 11, 2014                                        E. Wilde
                                                             UC Berkeley
                                                        February 7, 2014

                      The Accept-Post HTTP Header
                       draft-wilde-accept-post-02

Abstract

   This specification defines a new HTTP response header field Accept-
   Post, which indicates server support for specific media types for
   entity bodies in HTTP POST requests.

Note to Readers

   This draft should be discussed on the apps-discuss mailing list [1].

   Online access to all versions and files is available on github [2].

Status of this Memo

   This Internet-Draft is submitted 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 August 11, 2014.

Copyright Notice

   Copyright (c) 2014 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

Arwe, et al.             Expires August 11, 2014                [Page 1]
Internet-Draft                 Accept-Post                 February 2014

   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.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  The Accept-Post Response Header Field  . . . . . . . . . . . .  3
   4.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  4
     4.1.  The Accept-Post Response Header  . . . . . . . . . . . . .  4
   5.  Examples . . . . . . . . . . . . . . . . . . . . . . . . . . .  4
     5.1.  Atom Publishing Protocol . . . . . . . . . . . . . . . . .  4
     5.2.  Linked Data Platform . . . . . . . . . . . . . . . . . . .  5
     5.3.  Additional Information in Error Responses  . . . . . . . .  5
   6.  Implementation Status  . . . . . . . . . . . . . . . . . . . .  5
     6.1.  Eclipse Lyo  . . . . . . . . . . . . . . . . . . . . . . .  6
     6.2.  RWW.I/O  . . . . . . . . . . . . . . . . . . . . . . . . .  7
     6.3.  Tivoli Workload Automation . . . . . . . . . . . . . . . .  7
     6.4.  Jazz for Service Management  . . . . . . . . . . . . . . .  8
   7.  Security Considerations  . . . . . . . . . . . . . . . . . . .  9
   8.  Open Issues  . . . . . . . . . . . . . . . . . . . . . . . . .  9
   9.  Change Log . . . . . . . . . . . . . . . . . . . . . . . . . .  9
     9.1.  From -01 to -02  . . . . . . . . . . . . . . . . . . . . .  9
     9.2.  From -00 to -01  . . . . . . . . . . . . . . . . . . . . . 10
   10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10
     10.1. Normative References . . . . . . . . . . . . . . . . . . . 10
     10.2. Informative References . . . . . . . . . . . . . . . . . . 10
   Appendix A.  Acknowledgements  . . . . . . . . . . . . . . . . . . 11
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12

Arwe, et al.             Expires August 11, 2014                [Page 2]
Internet-Draft                 Accept-Post                 February 2014

1.  Introduction

   This specification defines a new HTTP response header field Accept-
   Post, which indicates server support for specific media types for
   entity bodies in HTTP POST requests.  This header field is comparable
   to the Accept-Patch response header field specified together with the
   HTTP PATCH method [RFC5789] (notice, however, that while Accept-Patch
   is defined to only list specific media types, Accept-Post reuses the
   "media range" concept of HTTP's Accept header and thus allows media
   type wildcards as well).

2.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
Show full document text