Registration Request for the respond-for HTTP preference

irakli <> Mon, 08 June 2020 04:54 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4E2803A0477 for <>; Sun, 7 Jun 2020 21:54:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.647
X-Spam-Status: No, score=-1.647 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id maV7Eoy45Md3 for <>; Sun, 7 Jun 2020 21:54:05 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id C33873A0484 for <>; Sun, 7 Jun 2020 21:54:05 -0700 (PDT)
Received: from lists by with local (Exim 4.92) (envelope-from <>) id 1ji9kz-0000Og-5P for; Mon, 08 Jun 2020 04:51:33 +0000
Resent-Message-Id: <>
Received: from www-data by with local (Exim 4.92) (envelope-from <>) id 1ji9kx-0000Np-7X for; Mon, 08 Jun 2020 04:51:31 +0000
Received: from ([]) by with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <>) id 1ji31i-00019R-5t for; Sun, 07 Jun 2020 21:40:22 +0000
Received: from ([]) by with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <>) id 1ji31g-0001E2-Ll for; Sun, 07 Jun 2020 21:40:22 +0000
Received: from ([] helo=[]) by with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <>) id 1ji31g-0003eg-8C for; Sun, 07 Jun 2020 21:40:20 +0000
Content-Type: multipart/alternative; boundary="Apple-Mail=_6160A3A8-DEF3-42D2-8485-9ECC9D09EE75"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.\))
From: irakli <>
Resent-From: Yves Lafon <>
Date: Tue, 28 Apr 2020 02:06:31 +0000
Resent-Date: Sun, 7 Jun 2020 23:40:17 +0200
Message-Id: <>
X-Name-Md5: efe3dad792d606410c9cc49cedaffc94
X-Mailer: Apple Mail (2.3608.
X-W3C-Hub-Spam-Status: No, score=0.3
X-W3C-Scan-Sig: 1ji31g-0001E2-Ll 73986d04fa022062b0e54c483b2a00a0
X-caa-id: 210b9fa691
Subject: Registration Request for the respond-for HTTP preference
Archived-At: <>
X-Mailing-List: <> archive/latest/37729
Precedence: list
List-Id: <>
List-Help: <>
List-Post: <>
List-Unsubscribe: <>

   o  Preference: respond-for

   o  Value: any alpha-numeric value. Dashes are also allowed.

   o  Optional Parameters: None

   o  Description: Expanded version of the "return" preference that 
allows clients to hint to the server the use-case for the response.
This allows batching response variations by common use-cases. The goal
is similar to GraphQL: letting client choose which data it needs, but
is significantly more light-weight and can allow all that client needs
in a very wide variety of cases, without resorting to heavier and 
potentially riskier GraphQL approach. For instance, for a blog post
a client may request "respond-for: teaser" or "respond-for: full-post"  

   o  Reference: <>

   o  Notes: We have used this approach successfully at a number of 
companies over the years but would like to standardize the preference
rather than using an unregistered preference, or using the "return" 
preference with values that are non-standard.

Thank you!

Irakli Nadareishvili