- From: Mark Nottingham <mnot@mnot.net>
- Date: Tue, 13 Feb 2018 13:47:02 +1100
- To: HTTP Working Group <ietf-http-wg@w3.org>
- Message-Id: <1B9ED3CE-99C8-4832-873B-0280B4931DFA@mnot.net>
Hello everyone, FYI, a fairly substantially updated Variants. Pretty version at: https://mnot.github.io/I-D/variants/ There is now a prototype implementation of the algorithms at: https://github.com/mnot/variants-toy ... which resulted in many of the changes. Negotiation for format (Accept) is now also supported. Feedback very much appreciated. Cheers, > Begin forwarded message: > > From: internet-drafts@ietf.org > Subject: New Version Notification for draft-nottingham-variants-02.txt > Date: 13 February 2018 at 1:44:33 pm AEDT > To: "Mark Nottingham" <mnot@mnot.net> > > > A new version of I-D, draft-nottingham-variants-02.txt > has been successfully submitted by Mark Nottingham and posted to the > IETF repository. > > Name: draft-nottingham-variants > Revision: 02 > Title: HTTP Representation Variants > Document date: 2018-02-13 > Group: Individual Submission > Pages: 19 > URL: https://www.ietf.org/internet-drafts/draft-nottingham-variants-02.txt > Status: https://datatracker.ietf.org/doc/draft-nottingham-variants/ > Htmlized: https://tools.ietf.org/html/draft-nottingham-variants-02 > Htmlized: https://datatracker.ietf.org/doc/html/draft-nottingham-variants-02 > Diff: https://www.ietf.org/rfcdiff?url2=draft-nottingham-variants-02 > > Abstract: > This specification introduces an alternative way to communicate a > secondary cache key for a HTTP resource, using the HTTP "Variants" > and "Variant-Key" response header fields. Its aim is to make HTTP > proactive content negotiation more cache-friendly. > > > > > Please note that it may take a couple of minutes from the time of submission > until the htmlized version and diff are available at tools.ietf.org. > > The IETF Secretariat > -- Mark Nottingham https://www.mnot.net/
Received on Tuesday, 13 February 2018 02:47:37 UTC