HTTP Origin and Hop Hints and Prefer Header

James M Snell <jasnell@gmail.com> Tue, 12 February 2013 17:02 UTC

Resent-Date: Tue, 12 Feb 2013 17:00:42 +0000
Resent-Message-Id: <E1U5JDm-0003r1-Vs@frink.w3.org>
MIME-Version: 1.0
From: James M Snell <jasnell@gmail.com>
Date: Tue, 12 Feb 2013 08:59:44 -0800
Message-ID: <CABP7Rbe7Y7KRVcnL9263KjmNB1k5gfvapXQfFjz5i2iK3kMhZQ@mail.gmail.com>
To: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>, Mark Nottingham <mnot@mnot.net>
Content-Type: text/plain; charset="UTF-8"
Received-SPF: pass client-ip=209.85.219.47; envelope-from=jasnell@gmail.com; helo=mail-oa0-f47.google.com
Subject: HTTP Origin and Hop Hints and Prefer Header
Archived-At: <http://www.w3.org/mid/CABP7Rbe7Y7KRVcnL9263KjmNB1k5gfvapXQfFjz5i2iK3kMhZQ@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list

Mark,

The most recent draft looks good. One thing that struck me is that
there seems to be a good alignment between this and the Prefer header.
Currently, there is no way for a client to know whether or not a
server supports Prefer. Hints would be a great way to provide that
information.

For instance...

Async-Responses

   o  Hint Name: pa
   o  Hint Type: origin
   o  Description: When true, indicates that the origin supports
Prefer: respond-async
   o  Value Type: boolean
   o  Contact: jasnell@gmail.com

Minimal Responses

   o  Hint Name: pr
   o  Hint Type: origin
   o  Description: When true, indicates that the origin supports
Prefer: return-minimal and return=representation
   o  Value Type: boolean
   o  Contact: jasnell@gmail.com

Strict and Lenient Handling

   o  Hint Name: ph
   o  Hint Type: origin
   o  Description: When true, indicates that the origin supports
Prefer: handling=strict and handling=lenient
   o  Value Type: boolean
   o  Contact: jasnell@gmail.com

- James

HTTP Origin and Hop Hints and Prefer Header James M Snell
Re: HTTP Origin and Hop Hints and Prefer Header Mark Nottingham