HTTP Request Media Query Headers for HTTP2 Push hinting

Bobby Mozumder <bmozumder@gmail.com> Tue, 11 April 2017 03:31 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCE4C1294FF for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 10 Apr 2017 20:31:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.502
X-Spam-Level:
X-Spam-Status: No, score=-6.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bn5CTS4qy6jP for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 10 Apr 2017 20:31:06 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7A541241FC for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 10 Apr 2017 20:22:27 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1cxmK9-0003PI-Pm for ietf-http-wg-dist@listhub.w3.org; Tue, 11 Apr 2017 03:18:33 +0000
Resent-Date: Tue, 11 Apr 2017 03:18:33 +0000
Resent-Message-Id: <E1cxmK9-0003PI-Pm@frink.w3.org>
Received: from titan.w3.org ([128.30.52.76]) by frink.w3.org with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <bmozumder@gmail.com>) id 1cxmK6-0003OO-Ul for ietf-http-wg@listhub.w3.org; Tue, 11 Apr 2017 03:18:30 +0000
Received: from mail-qt0-f175.google.com ([209.85.216.175]) by titan.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from <bmozumder@gmail.com>) id 1cxmK0-0001iC-P4 for ietf-http-wg@w3.org; Tue, 11 Apr 2017 03:18:25 +0000
Received: by mail-qt0-f175.google.com with SMTP id c45so79412762qtb.1 for <ietf-http-wg@w3.org>; Mon, 10 Apr 2017 20:18:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:content-transfer-encoding:mime-version:subject:message-id:date :to; bh=tVcP5o7bz0XDRPSFKzTnNm8EPwAawhuPjZRMzlepAOg=; b=iYlZYrpIYmp0bCq1MTtIOnZDJTrkIRr/oBOS+uqTxAGAeITxakE8jhR+T73FtDm7Yo T5HwoxiweM8NzoLFdsqA+HG+9+hBIeJXBEPj5f5GWxeO6pxFrBtvog20/xTUOo6UkL4X 4LimaslmJyCsyR54jEHNB+B5VcK8XsZ0+8qPUgqhwd8g46Fm7aR4qICm9zvF8aVub4Pj OpjFObek11DhAHmtxSoJfzszoHskUFeci10Pdxo1fIwQhil0ZhaBgpAWOftZR+9Vol+U TTJ3yjbR6S8fiFNuoIimjvuf6Log8HGXjSKIfu3uk9ODz2uKxfGyL0dGLv3Zc3OQUM5T g7XQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:message-id:date:to; bh=tVcP5o7bz0XDRPSFKzTnNm8EPwAawhuPjZRMzlepAOg=; b=X28xc8LgwnL10goKfwngOSSUqq2pG6dTrWhQMFo4Pm/lnu4Jv1b0Oh9wH6/4U5bvNT 6yyzJxpUA8foLv67pbQ21cLJyEAQM17cMvmu/Ocj4QkG2gPYuKL1Hxx0uHFBzS1lB1X7 WjLXnhaVIT4KuVpEi+7QKoRO0mizWYFK4xqyPCihoJYBKpiYJ3QzblIbxetROKfUxYpU Rekv59eaPoetW3SbmhIk/cFdOqPVvN635nn28CKB1XQZwZXqGWpTrNUXoZhIOJdDQeUy tH3XCShQ8ws1Ex+LURmjIEFnrsoscZ7IatgKgzGe6jmSmIFEDZg/su3TcVy+SKknAnVF Vv1Q==
X-Gm-Message-State: AN3rC/5L9I3pD/8DtnR9db7IWjwitxFCQa5hQZLKU7rgBK9CoK5Lx93+FMPn7DGjd8sxXw==
X-Received: by 10.200.56.155 with SMTP id f27mr10345831qtc.153.1491880678505; Mon, 10 Apr 2017 20:17:58 -0700 (PDT)
Received: from [10.0.1.5] (static-71-126-153-54.washdc.fios.verizon.net. [71.126.153.54]) by smtp.gmail.com with ESMTPSA id z29sm10146479qtz.67.2017.04.10.20.17.57 for <ietf-http-wg@w3.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 10 Apr 2017 20:17:57 -0700 (PDT)
From: Bobby Mozumder <bmozumder@gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Message-Id: <AEDA95C1-46AD-406C-AF5B-BEEC471A1C69@gmail.com>
Date: Mon, 10 Apr 2017 23:17:56 -0400
To: ietf-http-wg@w3.org
X-Mailer: Apple Mail (2.3273)
Received-SPF: pass client-ip=209.85.216.175; envelope-from=bmozumder@gmail.com; helo=mail-qt0-f175.google.com
X-W3C-Hub-Spam-Status: No, score=-3.0
X-W3C-Hub-Spam-Report: AWL=0.500, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: titan.w3.org 1cxmK0-0001iC-P4 831a7ec413c47c8ccfdb62aef87f71d1
X-Original-To: ietf-http-wg@w3.org
Subject: HTTP Request Media Query Headers for HTTP2 Push hinting
Archived-At: <http://www.w3.org/mid/AEDA95C1-46AD-406C-AF5B-BEEC471A1C69@gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/33806
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

Hi,

I’ve been using HTTP/2 push for a bit now, mostly for font push, and it’s been great.  I’m now trying to expand on other resources to push, including images.

Right now, it seems like an impossible task with the HTML PICTURE element, where we don’t know which sizes/format of an image that a client would need.  The HTML PICTURE element provides a list of all sorts of possible sizes/resolutions/formats of a single image, and the client picks one of them to download based on window height/width & browser capabilities.

Would it be possible to add standard HTTP request headers to indicate to the server the client media capabilities - resolution, size, etc..?  This is then complicated by the fact that the browser might change its client window size, or some items might already be cached.

Thank you,

-bobby