Re: [apps-discuss] informal Last Call on draft-reschke-http-status-308-02

Bjoern Hoehrmann <> Sat, 14 January 2012 16:51 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C1E4121F8542 for <>; Sat, 14 Jan 2012 08:51:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.31
X-Spam-Status: No, score=-2.31 tagged_above=-999 required=5 tests=[AWL=-0.311, BAYES_00=-2.599, J_CHICKENPOX_23=0.6]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 9FtzVu4FpbUB for <>; Sat, 14 Jan 2012 08:51:16 -0800 (PST)
Received: from ( []) by (Postfix) with SMTP id DC23221F8483 for <>; Sat, 14 Jan 2012 08:51:15 -0800 (PST)
Received: (qmail invoked by alias); 14 Jan 2012 16:51:11 -0000
Received: from (EHLO HIVE) [] by (mp014) with SMTP; 14 Jan 2012 17:51:11 +0100
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX1+fcVdCqp+fNWxu90y7zGeGFBxFvbSz8E70IzI0bO WgR0OamYgQnv3+
From: Bjoern Hoehrmann <>
To: Julian Reschke <>
Date: Sat, 14 Jan 2012 17:51:17 +0100
Message-ID: <>
References: <> <> <> <> <> <>
In-Reply-To: <>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
Cc: HTTP Working Group <>, IETF Apps Discuss <>
Subject: Re: [apps-discuss] informal Last Call on draft-reschke-http-status-308-02
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 14 Jan 2012 16:51:16 -0000

* Julian Reschke wrote:
>On 2012-01-14 16:48, Bjoern Hoehrmann wrote:
>> * Julian Reschke wrote:
>>> - what's the problem with the title?
>> When the redirect target disappears but the redirect does not, then you
>> might end up with "Permanent Redirect" as title in search results which
>> looks very broken and is uninformative. A better title would be "Moved
>> to<new location>".
>3xx responses never should show up in search results. Or am I missing 

When all of http://schnitzelmitkartoffelsalat.example/ redirects to some
address the search engine cannot connect to, and someone searches for,
say, "schnitzelmitkartoffelsalat.example", the search engine might still
list the site in the results, and might link the proper address instead
of the redirect target which it cannot resolve (reasons include that the
user might be able to connect to sites the search engine can't connect

>>> - why do I need to specify encoding? It's all US-ASCII
>> Because RFC 2854 says it's strongly recommended to use the parameter.
>Well, it's a silly recommendation in this case. And it's NOT UPPERCASE!

If you really want to argue that the example is better when it does not
declare the character encoding without very clearly indicating that the
declaration has been elided because it's "all US-ASCII" ... Do you still
keep Internet Explorer 6 around? It should be possible to make an ex-
ample that does not redirect to where you think it would, but I would
have to set up a virtual machine for testing and there kinda would be no
point if you don't have the right browser to try it.
Björn Höhrmann · ·
Am Badedeich 7 · Telefon: +49(0)160/4415681 ·
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 ·