draft-ietf-httpbis-rfc7238bis-02.txt   draft-ietf-httpbis-rfc7238bis-03.txt 
HTTPbis Working Group J. Reschke HTTPbis Working Group J. Reschke
Internet-Draft greenbytes Internet-Draft greenbytes
Obsoletes: 7238 (if approved) January 14, 2015 Obsoletes: 7238 (if approved) February 5, 2015
Intended status: Standards Track Intended status: Standards Track
Expires: July 18, 2015 Expires: August 9, 2015
The Hypertext Transfer Protocol Status Code 308 (Permanent Redirect) The Hypertext Transfer Protocol Status Code 308 (Permanent Redirect)
draft-ietf-httpbis-rfc7238bis-02 draft-ietf-httpbis-rfc7238bis-03
Abstract Abstract
This document specifies the additional Hypertext Transfer Protocol This document specifies the additional Hypertext Transfer Protocol
(HTTP) status code 308 (Permanent Redirect). (HTTP) status code 308 (Permanent Redirect).
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
skipping to change at page 1, line 32 skipping to change at page 1, line 32
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 July 18, 2015. This Internet-Draft will expire on August 9, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 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 13 skipping to change at page 2, line 13
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Notational Conventions . . . . . . . . . . . . . . . . . . . . 3 2. Notational Conventions . . . . . . . . . . . . . . . . . . . . 3
3. 308 Permanent Redirect . . . . . . . . . . . . . . . . . . . . 3 3. 308 Permanent Redirect . . . . . . . . . . . . . . . . . . . . 3
4. Deployment Considerations . . . . . . . . . . . . . . . . . . . 4 4. Deployment Considerations . . . . . . . . . . . . . . . . . . . 4
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 5 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6
8.1. Normative References . . . . . . . . . . . . . . . . . . . 6 8.1. Normative References . . . . . . . . . . . . . . . . . . . 6
8.2. Informative References . . . . . . . . . . . . . . . . . . 6 8.2. Informative References . . . . . . . . . . . . . . . . . . 6
1. Introduction 1. Introduction
HTTP defines a set of status codes for the purpose of redirecting a HTTP defines a set of status codes for the purpose of redirecting a
request to a different URI ([RFC3986]). The history of these status request to a different URI ([RFC3986]). The history of these status
codes is summarized in Section 6.4 of [RFC7231], which also codes is summarized in Section 6.4 of [RFC7231], which also
classifies the existing status codes into four categories. classifies the existing status codes into four categories.
skipping to change at page 5, line 33 skipping to change at page 5, line 33
>http://example.com/new</a>. >http://example.com/new</a>.
</p> </p>
</body> </body>
</html> </html>
5. Security Considerations 5. Security Considerations
All security considerations that apply to HTTP redirects apply to the All security considerations that apply to HTTP redirects apply to the
308 status code as well (see Section 9 of [RFC7231]). 308 status code as well (see Section 9 of [RFC7231]).
Unsecured communication over the Internet is subject to man in the
middle modification of messages, including changing status codes or
redirect targets. Use of TLS is one way to mitigate those attacks.
See Section 9 of [RFC7230] for related attacks on authority and
message integrity.
6. IANA Considerations 6. IANA Considerations
The "Hypertext Transfer Protocol (HTTP) Status Code Registry" The "Hypertext Transfer Protocol (HTTP) Status Code Registry"
(defined in Section 8.2 of [RFC7231] and located at (defined in Section 8.2 of [RFC7231] and located at
<http://www.iana.org/assignments/http-status-codes>) needs to be <http://www.iana.org/assignments/http-status-codes>) needs to be
updated with the registration below: updated with the registration below:
+-------+--------------------+---------------------------------+ +-------+--------------------+---------------------------------+
| Value | Description | Reference | | Value | Description | Reference |
+-------+--------------------+---------------------------------+ +-------+--------------------+---------------------------------+
| 308 | Permanent Redirect | Section 3 of this specification | | 308 | Permanent Redirect | Section 3 of this specification |
+-------+--------------------+---------------------------------+ +-------+--------------------+---------------------------------+
7. Acknowledgements 7. Acknowledgements
The definition for the new status code 308 reuses text from the The definition for the new status code 308 reuses text from the
HTTP/1.1 definitions of status codes 301 and 307. HTTP/1.1 definitions of status codes 301 and 307.
Furthermore, thanks to Ben Campbell, Cyrus Daboo, Adrian Farrell, Furthermore, thanks to Ben Campbell, Cyrus Daboo, Adrian Farrell,
Eran Hammer-Lahav, Bjoern Hoehrmann, Barry Leiba, Subramanian Eran Hammer-Lahav, Bjoern Hoehrmann, Barry Leiba, Subramanian
Moonesamy, Peter Saint-Andre, and Robert Sparks for feedback on this Moonesamy, Kathleen Moriarty, Peter Saint-Andre, Robert Sparks, and
document. Roy Fielding for feedback on this document.
8. References 8. References
8.1. Normative References 8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform [RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform
Resource Identifier (URI): Generic Syntax", STD 66, Resource Identifier (URI): Generic Syntax", STD 66,
 End of changes. 7 change blocks. 
7 lines changed or deleted 13 lines changed or added

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