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

The Hypertext Transfer Protocol (HTTP) Status Code 308 (Permanent Redirect)
draft-reschke-http-status-308-07

Document type: Active Internet-Draft (individual in app area)
Document stream: IETF
Last updated: 2012-04-20 (latest revision 2012-03-26)
Intended RFC status: Experimental
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: Cyrus Daboo (cyrus@daboo.name) is the document shepherd.
Send notices to: julian.reschke@greenbytes.de, cyrus@daboo.name, draft-reschke-http-status-308@tools.ietf.org, stpeter@stpeter.im

Network Working Group                                         J. Reschke
Internet-Draft                                                greenbytes
Intended status: Experimental                             March 26, 2012
Expires: September 27, 2012

   The Hypertext Transfer Protocol (HTTP) Status Code 308 (Permanent
                               Redirect)
                    draft-reschke-http-status-308-07

Abstract

   This document specifies the additional HyperText Transfer Protocol
   (HTTP) Status Code 308 (Permanent Redirect).

Editorial Note (To be removed by RFC Editor before publication)

   Distribution of this document is unlimited.  Although this is not a
   work item of the HTTPbis Working Group, comments should be sent to
   the Hypertext Transfer Protocol (HTTP) mailing list at
   ietf-http-wg@w3.org [1], which may be joined by sending a message
   with subject "subscribe" to ietf-http-wg-request@w3.org [2].

   Discussions of the HTTPbis Working Group are archived at
   <http://lists.w3.org/Archives/Public/ietf-http-wg/>.

   XML versions, latest edits, and the issues list for this document are
   available from
   <http://greenbytes.de/tech/webdav/#draft-reschke-http-status-308>.

   Test cases related to redirection in general and the status code 308
   in particular can be found at
   <http://greenbytes.de/tech/tc/httpredirects/#l-308>.

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."

Reschke                Expires September 27, 2012               [Page 1]
Internet-Draft            HTTP Status Code 308                March 2012

   This Internet-Draft will expire on September 27, 2012.

Copyright Notice

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Notational Conventions  . . . . . . . . . . . . . . . . . . . . 3
   3.  308 Permanent Redirect  . . . . . . . . . . . . . . . . . . . . 3
   4.  Deployment Considerations . . . . . . . . . . . . . . . . . . . 4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . . . 5
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 5
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 6
     8.1.  Normative References  . . . . . . . . . . . . . . . . . . . 6
     8.2.  Informative References  . . . . . . . . . . . . . . . . . . 6
   Appendix A.  Implementations (to be removed by RFC Editor
                before publication)  . . . . . . . . . . . . . . . . . 7
   Appendix B.  Change Log (to be removed by RFC Editor before
                publication) . . . . . . . . . . . . . . . . . . . . . 7
     B.1.  Since draft-reschke-http-status-308-00  . . . . . . . . . . 7
     B.2.  Since draft-reschke-http-status-308-01  . . . . . . . . . . 7
     B.3.  Since draft-reschke-http-status-308-02  . . . . . . . . . . 7
     B.4.  Since draft-reschke-http-status-308-03  . . . . . . . . . . 7
     B.5.  Since draft-reschke-http-status-308-04  . . . . . . . . . . 7
     B.6.  Since draft-reschke-http-status-308-05  . . . . . . . . . . 8
     B.7.  Since draft-reschke-http-status-308-06  . . . . . . . . . . 8
   Appendix C.  Resolved issues (to be removed by RFC Editor
                before publication)  . . . . . . . . . . . . . . . . . 8
     C.1.  consistency307  . . . . . . . . . . . . . . . . . . . . . . 8
     C.2.  sniffing  . . . . . . . . . . . . . . . . . . . . . . . . . 8
   Appendix D.  Open issues (to be removed by RFC Editor prior to

[include full document text]