Re: [Ietf-message-headers] HTTP Refresh header
Julian Reschke <julian.reschke@gmx.de> Wed, 09 August 2017 18:29 UTC
Return-Path: <julian.reschke@gmx.de>
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 85BB3132448 for <ietf-message-headers@ietfa.amsl.com>; Wed, 9 Aug 2017 11:29:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.9
X-Spam-Level:
X-Spam-Status: No, score=-4.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=ham 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 Jtn9ANSiq6x1 for <ietf-message-headers@ietfa.amsl.com>; Wed, 9 Aug 2017 11:29:04 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (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 B59C61323B4 for <ietf-message-headers@lists.ietf.org>; Wed, 9 Aug 2017 11:29:03 -0700 (PDT)
Received: from [192.168.178.20] ([93.217.96.135]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MePYV-1dzVQ71qN5-00Q8Cw; Wed, 09 Aug 2017 20:28:56 +0200
To: Mark Nottingham <mnot@mnot.net>
Cc: Anne van Kesteren <annevk@annevk.nl>, ietf-message-headers@lists.ietf.org
References: <CADnb78jQHnrsjpXYZQCQt1kcaRTxWSJWDyyF74os6FPvshyPZg@mail.gmail.com> <1c5ce02a-9312-34e5-35b8-b5e1ba6089d4@gmx.de> <0C07550D-D9AD-4095-9A58-C027D8B49A17@mnot.net>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <b50537c8-cbbc-25bd-c67e-471734384e44@gmx.de>
Date: Wed, 09 Aug 2017 20:28:56 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <0C07550D-D9AD-4095-9A58-C027D8B49A17@mnot.net>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:5vT4dGA/1pga794yFD7XtGURahdmq/JQzjN3I4UqMRasuLTf3ej 3yb/rc0/CkigTAAInaFJ4+yKtBxhalH/WSfgT8ZE+GoAD4cQe2y06slhcRP8j6YlHEnB5OV HuBXX2Rw8ferpjhidXwDZXrbtOBE/UafI+M0JmShhDouriDC5f/2Pjc2bOe5kjHnykLL7rE u6S1cydZjUbnN4KvmpGMA==
X-UI-Out-Filterresults: notjunk:1;V01:K0:A26dd4mfoE8=:ApAsfTo/ZVGwC4vB+pUiSB fu6Lo4Qmh8g73mzJOcc3DseAoq1QOwQ5C4ASSN+PFPGooqP3c9GEJVoMoxz66sVnEzmFjRgbd KK9pbIwf2d9YfPHZRqPnH6qlW2KWSSM4Gqmx5l6o547SOWtZZWJTVV5BSaJADX5s+/LQ/jyY8 yTonQomo/npyxKjpkZ55zLrqT5wGz5hlJWYWeVx6Vo0dnbAeVXrX2dkGpUTET3QJT2BcP/2qG 0/VbuG08yUEB1Rw4vO+ix8bk/Yznz28MRT3v+XHLClQaLFq4Wg8IjxQv06HeZ7wqsTxhDD/Qg hNqqlTrVNkM7yHQMucE7bWiiZ83TRahgSJPaDtXRGBVPBBJp9J0r3e8cBiTBA2j06t2yXySNy qmkkxsnRS4SaQ6avLc1+fe2f5Hg8mml/HZAsADoZ/qNiPABNkwaMGRCSDk0BtbJLUxUtdtX1o waWHvYlT4uHdoA5kWmQfYbYZy4aGeknPmJbD4u/Qlw5Jyt+ZUWrR7qXKa6jJNXqtLKbZALxsW x2C6jDIlP7Sae05f1SksIcsbzw2lIoWucrJDzVPAlQulc7bFxKlPtOnfec/CCHFLtB3u4ppPE zRSo4wpmFJSlhnJPrJp7mKeLAaVvJselphzd74g9twp0nhG4WRfG7O62jmbPGAzDXtqUPChg2 G3Ih5OzvImJwQYd530KKEImTxqpPkVsAIE+B0WzL3d8TIum7xsP9KSfdslfZaQ+rY8KWigMHp cghUotox0/rcXHRBcpKuq+ogvr1CPhK8jHy7hfawM8mDa02VfBuzSikGux6SnpAm/o99UOsM/ ro77Wpk3ADdDwAL0L60yB2P/TEx+guobf303u64fxitPzhB6Yo=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-message-headers/5lWuvEZPNTB8gOMmlBv2D0FF6rY>
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:29:05 -0000
On 2017-08-09 20:02, Mark Nottingham wrote: > 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. > ... That is true, but the registration actually should reference something that specifies the HTTP header field. Best regards, Julian
- [Ietf-message-headers] HTTP Refresh header Anne van Kesteren
- Re: [Ietf-message-headers] HTTP Refresh header Julian Reschke
- Re: [Ietf-message-headers] HTTP Refresh header Mark Nottingham
- Re: [Ietf-message-headers] HTTP Refresh header Julian Reschke
- Re: [Ietf-message-headers] HTTP Refresh header Anne van Kesteren
- Re: [Ietf-message-headers] HTTP Refresh header Julian Reschke
- Re: [Ietf-message-headers] HTTP Refresh header Anne van Kesteren
- Re: [Ietf-message-headers] HTTP Refresh header Graham Klyne
- Re: [Ietf-message-headers] HTTP Refresh header Anne van Kesteren