p6: Warning header field
"Roy T. Fielding" <fielding@gbiv.com> Sun, 09 June 2013 07:25 UTC
Return-Path: <ietf-http-wg-request@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 0D64121F91A3 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sun, 9 Jun 2013 00:25:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aNipxr4sHw8s for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sun, 9 Jun 2013 00:24:54 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id 6AE7521F8AE8 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Sun, 9 Jun 2013 00:24:53 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1UlZxs-0008Rm-Gj for ietf-http-wg-dist@listhub.w3.org; Sun, 09 Jun 2013 07:23:00 +0000
Resent-Date: Sun, 09 Jun 2013 07:23:00 +0000
Resent-Message-Id: <E1UlZxs-0008Rm-Gj@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <fielding@gbiv.com>) id 1UlZxZ-0008QD-5x for ietf-http-wg@listhub.w3.org; Sun, 09 Jun 2013 07:22:41 +0000
Received: from caiajhbdcbbj.dreamhost.com ([208.97.132.119] helo=homiemail-a98.g.dreamhost.com) by maggie.w3.org with esmtp (Exim 4.72) (envelope-from <fielding@gbiv.com>) id 1UlZxY-0004qb-CI for ietf-http-wg@w3.org; Sun, 09 Jun 2013 07:22:41 +0000
Received: from homiemail-a98.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a98.g.dreamhost.com (Postfix) with ESMTP id DA84F2C2059 for <ietf-http-wg@w3.org>; Sun, 9 Jun 2013 00:22:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=gbiv.com; h=from :content-type:content-transfer-encoding:subject:date:message-id :to:mime-version; s=gbiv.com; bh=Y4/LmrrY093bixqFqXE/I9FxL1w=; b=v75BXxqwHHl5YpkYVKYpI0EzitYTqMWavrC6XF4VwPSaHy7mmazW7kr/cMFRG n8f64QYEOd6dtIVeVmZgAFMLm7SblxJijjzcgqFNu5HXvIyeZJZXGAX3m8MGt8S/ tmgUfh2esVYa1fsg02jzLkxm8xm4QCrMvWQOqmn2HHZOL8=
Received: from [192.168.1.84] (99-21-208-82.lightspeed.irvnca.sbcglobal.net [99.21.208.82]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: fielding@gbiv.com) by homiemail-a98.g.dreamhost.com (Postfix) with ESMTPSA id BFD042C2058 for <ietf-http-wg@w3.org>; Sun, 9 Jun 2013 00:22:18 -0700 (PDT)
From: "Roy T. Fielding" <fielding@gbiv.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Date: Sun, 09 Jun 2013 00:22:17 -0700
Message-Id: <413C419A-AE9D-46F8-82A5-72B4341754AD@gbiv.com>
To: HTTP Working Group <ietf-http-wg@w3.org>
Mime-Version: 1.0 (Apple Message framework v1283)
X-Mailer: Apple Mail (2.1283)
Received-SPF: none client-ip=208.97.132.119; envelope-from=fielding@gbiv.com; helo=homiemail-a98.g.dreamhost.com
X-W3C-Hub-Spam-Status: No, score=-4.5
X-W3C-Hub-Spam-Report: AWL=-2.487, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001
X-W3C-Scan-Sig: maggie.w3.org 1UlZxY-0004qb-CI 91c1890bd5bba98c553e11731fcdccc3
X-Original-To: ietf-http-wg@w3.org
Subject: p6: Warning header field
Archived-At: <http://www.w3.org/mid/413C419A-AE9D-46F8-82A5-72B4341754AD@gbiv.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/18200
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>
I just noticed that the definition of the Warning header field includes a required host or pseudonym between the warn-code and the warn-text, and further that the warn-text is a quoted-string. Since there are no examples provided, and the table of warn-codes makes them look like status-code reason-phrase, it should be no surprise that implementations send things like Warning: 110 Response is stale Warning: 110 squid/3.2.0.5 "Response is stale" Warning: 111 squid/3.2.0.5 "Revalidation failed" Warning: 111 Revalidation failed Warning: 112 Disconnected Operation Warning: 214 host.example.com Transformation applied In fact, the only places I can find correctly formatted Warning header fields is in an internal Apache debugging module (mod_policy, abusing that field for other means) and within a BEA example for SIP. Warning: 307 isi.edu "Session parameter 'foo' not understood" I haven't found any that send the optional warn-date. Obviously, examples are needed in p6, unless I can delete the header field and be done with it. ....Roy
- p6: Warning header field Roy T. Fielding
- Re: p6: Warning header field Mark Nottingham
- Re: #496, was: p6: Warning header field Julian Reschke
- #496, was: p6: Warning header field Julian Reschke
- Re: #496, was: p6: Warning header field Roy T. Fielding