HTTP Immutable Responses
draft-ietf-httpbis-immutable-00

Document Type Active Internet-Draft (httpbis WG)
Last updated 2017-01-12
Replaces draft-mcmanus-immutable
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Yes
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                         P. McManus
Internet-Draft                                                   Mozilla
Intended status: Standards Track                        January 12, 2017
Expires: July 16, 2017

                        HTTP Immutable Responses
                    draft-ietf-httpbis-immutable-00

Abstract

   The immutable HTTP response Cache-Control extension allows servers to
   identify resources that will not be updated during their freshness
   lifetime.  This assures that a client never needs to revalidate a
   cached fresh resource to be certain it has not been modified.

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 July 16, 2017.

Copyright Notice

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

McManus                   Expires July 16, 2017                 [Page 1]
Internet-Draft                     I-D                      January 2017

1.  Introduction

   The HTTP freshness lifetime [RFC7234] caching attribute specifies
   that a client may safely reuse a response to satisfy future requests
   over a specific period of time.  It does not specify that the
   resource will be not be modified during that period.

   For instance, a front page newspaper photo with a freshness lifetime
   of one hour would mean that no user should see a photo more than one
   hour old.  However, the photo could be updated at any time resulting
   in different users seeing different photos depending on the contents
   of their caches for up to one hour.  This is compliant with the
   caching mechanism defined in [RFC7234].

   Users that need to confirm there have been no updates to their
   current cached resources typically invoke the reload (or refresh)
   mechanism in the user agent.  This in turn generates a conditional
   request [RFC7232] and either a new representation or, if unmodified,
   a 304 response [RFC7231] is returned.  A user agent that manages HTML
   and its dependent sub-resources may issue hundreds of conditional
   requests to refresh all portions of a common HTML page [REQPERPAGE].

   Through the use of the versioned URL design pattern some content
   providers never create more than one variant of a sub-resource.  When
   these resources need an update they are simply published under a new
   URL, typically embedding a variant identifier in the path, and
   references to the sub-resource are updated with the new path
   information.

   For example, https://www.example.com/101016/main.css might be updated
   and republished as https://www.example.com/102026/main.css and the
   html that references it is changed at the same time.  This design
   pattern allows a very large freshness lifetime to be applied to the
   sub-resource without guessing when it will be updated in the future.

   Unfortunately, the user-agent is not aware of the versioned URL
   design pattern.  User driven refresh events still translate into
   wasted conditional requests for each sub-resource as each will return
   304 responses.

   The immutable HTTP response Cache-Control extension allows servers to
   identify resources that will not be updated during their freshness
   lifetime.  This effectively instructs the client that any conditional
   request for a previously served variant of that resource may be
   safely skipped without worrying that it has been updated.

McManus                   Expires July 16, 2017                 [Page 2]
Internet-Draft                     I-D                      January 2017
Show full document text