Re: [Ietf-message-headers] HTTP Refresh header

Mark Nottingham <mnot@mnot.net> Wed, 09 August 2017 18:02 UTC

Return-Path: <mnot@mnot.net>
X-Original-To: ietf-message-headers@ietfa.amsl.com
Delivered-To: ietf-message-headers@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6256132396 for <ietf-message-headers@ietfa.amsl.com>; Wed, 9 Aug 2017 11:02:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level:
X-Spam-Status: No, score=-2.721 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=Yr/i2O0X; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=MrOvKz8z
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 9xr_0-shJNgC for <ietf-message-headers@ietfa.amsl.com>; Wed, 9 Aug 2017 11:02:17 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 91E451321BF for <ietf-message-headers@lists.ietf.org>; Wed, 9 Aug 2017 11:02:17 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 2517620C9F; Wed, 9 Aug 2017 14:02:15 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute3.internal (MEProxy); Wed, 09 Aug 2017 14:02:15 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=fm1; bh=Mx/xOEG1JBlzUp9drR cH2LiZZ1Lql5YvY0cGAGYCcRc=; b=Yr/i2O0XZn+bOuvsXfcL5Gwu+Nubmsbruw Y73xHwoPkEh5BRHRJJZVjjkXxmpv6/R/tYS/Rh3rk3ruo7glwAqpSDnvngp7/XqB 8QdtoNLdILw+blMZV8i+0p8f3KM5NbC7Mr+CBnYWFk4EIoNbOBn/KUEIa9FqM4uD COm77AB3jmOobDIE7JoabwQYuqG7S8FyHSLYfkNenJ4XTY9KuWjF6uRAAkb7cXLD CBSN04DGhAo7KHY1P4cQChgpgg6Z5n76UlD2djPRS5BpWLauyanmb0JsGAPn0Wr4 uY7rWDe6FwniwfoM2GQAVRUIYBLr+C10+4mQj9hBISjrmNdtoOTA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=Mx/xOEG1JBlzUp9drRcH2LiZZ1Lql5YvY0cGAGYCcRc=; b=MrOvKz8z nl9kvcDjXPEdZCVAOZYP5fyn6iQSnaFNnyycoD6RoDWdqgLZoWj+MbOpOkT/R8cV dP7Jf7iCPIqBoVn+X3kWoSKh/WmTc6iNY/LkzbqSgnluSLpy2XXkhT4QS1r4iUlA AJ/4qZgDxgjiP/RjF0AAqNos4hSb2rkPKsT4Oba/zUAtMfgDiRwaY6LGcFmZ6Pu1 JAkFAa/n3kRylkzcgVLmUOciTAmdI+wOntLnPd/QjwK1QyRdegQLG/HYKfH0QXMa Wz4UG+TkmLgIoz0Vk12/lJVIkPA8x2DaTCegC99u5NqcCt+OU3y5RcJxRfi2X5r3 bCQ0JXKzVs5Bzg==
X-ME-Sender: <xms:J06LWWS1APtm1hqu4w72GZ5DBehGtaWhorf2CwB0GjtNxN8Bl0nwZg>
X-Sasl-enc: v5Y90M4XjC3gQvvwM3A+rG8FzaFksiL+5TsKnFw6T4HZ 1502301734
Received: from [10.100.20.227] (unknown [8.18.217.202]) by mail.messagingengine.com (Postfix) with ESMTPA id 9BB372524C; Wed, 9 Aug 2017 14:02:14 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <1c5ce02a-9312-34e5-35b8-b5e1ba6089d4@gmx.de>
Date: Wed, 9 Aug 2017 11:02:10 -0700
Cc: Anne van Kesteren <annevk@annevk.nl>, ietf-message-headers@lists.ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <0C07550D-D9AD-4095-9A58-C027D8B49A17@mnot.net>
References: <CADnb78jQHnrsjpXYZQCQt1kcaRTxWSJWDyyF74os6FPvshyPZg@mail.gmail.com> <1c5ce02a-9312-34e5-35b8-b5e1ba6089d4@gmx.de>
To: "Julian F. Reschke" <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-message-headers/ejSADL7u4aVIfgiy8-oh8Qn-Oz0>
Subject: Re: [Ietf-message-headers] HTTP Refresh header
X-BeenThere: ietf-message-headers@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussion list for header fields used in Internet messaging applications." <ietf-message-headers.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-message-headers>, <mailto:ietf-message-headers-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-message-headers/>
List-Post: <mailto:ietf-message-headers@ietf.org>
List-Help: <mailto:ietf-message-headers-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-message-headers>, <mailto:ietf-message-headers-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Aug 2017 18:02:20 -0000

It'd be nice if the header was well-defined, but those aren't requirements for registration; if it's in use (and it is), it should be registered.


> On 9 Aug 2017, at 10:58 am, Julian Reschke <julian.reschke@gmx.de> wrote:
> 
> On 2017-08-09 19:00, Anne van Kesteren wrote:
>> Header field name: Refresh
>> Applicable protocol: http
>> Status: standard
>> Author/Change controller: WHATWG
>> Specification document(s): https://html.spec.whatwg.org/
>> Related information: See
>> https://github.com/whatwg/html/commit/7e9f6b6ffe2119f43f909f71773a25a7e8a61ca7
>> if you're interested in the exact changes to the HTML Standard.
> 
> It's great that you're doing this, but I think the changes in the spec aren't sufficient at all in order to define the header field.
> 
> See <https://www.greenbytes.de/tech/webdav/rfc7231.html#considerations.for.new.header.fields>.
> 
> Best regards, Julian
> 
> _______________________________________________
> Ietf-message-headers mailing list
> Ietf-message-headers@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-message-headers

--
Mark Nottingham   https://www.mnot.net/