Fwd: Document Action: 'The Hypertext Transfer Protocol (HTTP) Status Code 308 (Permanent Redirect)' to Experimental RFC (draft-reschke-http-status-308-07.txt)

Could this 308 (Permanent Redirect) give us a way to cache a probe URI's
definition document location?

An issue people have with httpRange-14 is that 303 redirects can't be
cached. If we could agree to use a 308 response as a cache-able
alternative to 303, we could reduce server load and speed client URI
processing (by caching the result of a probe URI).

Thoughts?
James

-------- Original Message --------
Subject: Document Action: 'The Hypertext Transfer Protocol (HTTP)
Status Code 308 (Permanent Redirect)' to Experimental RFC
(draft-reschke-http-status-308-07.txt)
Date: Mon, 26 Mar 2012 00:50:54 -0700
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
CC: RFC Editor <rfc-editor@rfc-editor.org>

The IESG has approved the following document:
- 'The Hypertext Transfer Protocol (HTTP) Status Code 308 (Permanent
   Redirect)'
  (draft-reschke-http-status-308-07.txt) as an Experimental RFC

This document has been reviewed in the IETF but is not the product of an
IETF Working Group.

The IESG contact person is Peter Saint-Andre.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-reschke-http-status-308/




Technical Summary
    This document specifies the additional HyperText Transfer Protocol
    (HTTP) Status Code 308 (Permanent Redirect). This fills in a missing
    piece of HTTP redirect behavior by allowing for a permanent redirect
    that is guaranteed to not have a POST method changed to a GET.

Working Group Summary
    This document is not the product of a working group, however it has
    been discussed on the HTTP mailing list where ongoing HTTPbis work
    is carried out.

Document Quality
    This document has been discussed and reviewed on the HTTP mailing
    list (<ietf-http-wg@w3.org>) mailing list. Informal last calls were
    carried out on that mailing list as well as the IETF Apps Discuss
    list (<apps-discuss@ietf.org>). This specification simply registers
    a new HTTP status code that is a variant of existing well-defined
    codes, and as such is straightforward.

Received on Tuesday, 27 March 2012 01:16:12 UTC