HTTP Link and Unlink Methods
draft-snell-link-method-04
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2013-09-23
|
|
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)
|
Individual Submission J. Snell
Internet-Draft
Intended status: Standards Track September 23, 2013
Expires: March 27, 2014
HTTP Link and Unlink Methods
draft-snell-link-method-04
Abstract
This specification defines the semantics of the LINK and UNLINK HTTP
methods.
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 March 27, 2014.
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.
Snell Expires March 27, 2014 [Page 1]
Internet-Draft HTTP Link and Unlink Methods September 2013
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. LINK . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. UNLINK . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Relationship to other HTTP Methods and Discoverability of
Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
5. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
6. Security Considerations . . . . . . . . . . . . . . . . . . . 5
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
7.1. Normative References . . . . . . . . . . . . . . . . . . 5
7.2. Informational References . . . . . . . . . . . . . . . . 5
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5
1. Introduction
This specification updates the HTTP LINK and UNLINK methods
originally defined in [RFC2068].
In this document, the key words "MUST", "MUST NOT", "REQUIRED",
"SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",
and "OPTIONAL" are to be interpreted as described in [RFC2119].
2. LINK
The LINK method is used to establish one or more relationships
between the resource identified by the effective request URI and one
or more other resources. Metadata contained within Link header
fields [RFC5988] provide information about which other resources are
being connected to the target and the type of relationship being
established. A payload within a LINK request has no defined
semantics.
LINK requests are idempotent. For any pair of resources, exactly one
relationship of any given type can exist. However, multiple
relationships of different types can be established between the same
pair of resources.
LINK requests are not safe, however. Establishing a relationship
causes an inherent change to the state of the target resource.
Responses to LINK requests are not cacheable. If a LINK request
passes through a cache that has one or more stored responses for the
effective request URI, those stored responses will be invalidated
(see Section 6 of [I-D.ietf-httpbis-p6-cache]).
A single LINK request can contain multiple Link header fields, each
of which establishes a separate, independent relationship with the
Snell Expires March 27, 2014 [Page 2]
Internet-Draft HTTP Link and Unlink Methods September 2013
target resource. In such cases, the server MUST either create all of
the relationships or not create any of them.
3. UNLINK
The UNLINK method is used to remove one or more relationships between
the resource identified by the effective request URI and other
resources. Metadata contained within Link header fields [RFC5988]
provide the information about the relationships that are to be
removed. A payload within an UNLINK request has no defined
semantics.
UNLINK request messages are idempotent but are not safe. Removing a
relationship causes an inherent change to the state of the target
resource.
Responses to UNLINK requests are not cacheable. If an UNLINK request
passes through a cache that has one or more stored responses for the
Show full document text