Is the "as" needed in "early hints" response

Jevan Pipitone <email1@jevan.com.au> Sun, 25 June 2017 12:33 UTC

Return-Path: <email1@jevan.com.au>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CBE2127B60 for <ietf@ietfa.amsl.com>; Sun, 25 Jun 2017 05:33:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.737
X-Spam-Level:
X-Spam-Status: No, score=-0.737 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_IMAGE_ONLY_16=1.092, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_NEUTRAL=0.779, T_REMOTE_IMAGE=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 M6YbnV66wnrC for <ietf@ietfa.amsl.com>; Sun, 25 Jun 2017 05:33:20 -0700 (PDT)
Received: from aibo.runbox.com (aibo.runbox.com [91.220.196.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 436E91200ED for <ietf@ietf.org>; Sun, 25 Jun 2017 05:33:20 -0700 (PDT)
Received: from [10.9.9.210] (helo=mailfront10.runbox.com) by mailtransmit03.runbox with esmtp (Exim 4.86_2) (envelope-from <email1@jevan.com.au>) id 1dP6j6-0003o3-Qb for ietf@ietf.org; Sun, 25 Jun 2017 14:33:16 +0200
Received: from [121.127.210.125] (helo=desktop-797rgpq) by mailfront10.runbox.com with esmtpsa (uid:796123 ) (TLS1.0:DHE_RSA_3DES_EDE_CBC_SHA1:192) (Exim 4.82) id 1dP6j2-0004lx-87 for ietf@ietf.org; Sun, 25 Jun 2017 14:33:13 +0200
To: ietf@ietf.org
From: Jevan Pipitone <email1@jevan.com.au>
Subject: Is the "as" needed in "early hints" response
Message-ID: <d6c85dec-b232-453a-5476-2079fe5a8784@jevan.com.au>
Date: Sun, 25 Jun 2017 22:33:05 +1000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------2B49AC654154499A84F58FB3"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pwYfUjDP4bnCfnuPovleCe9EfXE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Jun 2017 12:33:22 -0000

Is the "as" needed in "early hints" response

What about if we had:

Server response:
       HTTP/1.1 103 Preload
       Link: </style.css>
       Link: </script.js>
       Loading: </ball.jpg>

since it doesn't matter what the content to be preloaded is, that will be determined later when the html page is sent. For example the case for type="javascript" since we don't actually know what type of script it is anyway from the "early hints" you mentioned, but that doesn't matter either.

Also we could have a "loading" item to display while the page is being loaded. This could be a jpg, gif, even a small flash file.

Date: Sun, 25 Jun 2017 12:11:29 +0200
From: Julian Reschke<julian.reschke@gmx.de>
...
Server response:
       HTTP/1.1 103 Early Hints
       Link: </style.css>; rel=preload; as=style
       Link: </script.js>; rel=preload; as=script
...