IETF Logo Mail Archive

RE: comments on draft-abarth-mime-sniff-03

Ian Hickson <ian@hixie.ch> Sat, 23 January 2010 06:32 UTC

Return-Path: <ian@hixie.ch>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3950D3A682A for <apps-discuss@core3.amsl.com>; Fri, 22 Jan 2010 22:32:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AlRA4LugH3jA for <apps-discuss@core3.amsl.com>; Fri, 22 Jan 2010 22:32:23 -0800 (PST)
Received: from looneymail-a1.g.dreamhost.com (caibbdcaaaaf.dreamhost.com [208.113.200.5]) by core3.amsl.com (Postfix) with ESMTP id 2EA4B3A6809 for <apps-discuss@ietf.org>; Fri, 22 Jan 2010 22:32:22 -0800 (PST)
Received: from ps20323.dreamhostps.com (ps20323.dreamhost.com [69.163.222.251]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by looneymail-a1.g.dreamhost.com (Postfix) with ESMTP id 58B7415D78B; Fri, 22 Jan 2010 22:32:18 -0800 (PST)
Date: Sat, 23 Jan 2010 06:32:18 +0000
From: Ian Hickson <ian@hixie.ch>
To: Larry Masinter <masinter@adobe.com>
Subject: RE: comments on draft-abarth-mime-sniff-03
In-Reply-To: <C68CB012D9182D408CED7B884F441D4D5FE353@nambxv01a.corp.adobe.com>
Message-ID: <Pine.LNX.4.64.1001230630450.19587@ps20323.dreamhostps.com>
References: <C68CB012D9182D408CED7B884F441D4D5FDE79@nambxv01a.corp.adobe.com> <7789133a1001201514l47b43b8bw958e42794707dbc9@mail.gmail.com> <C68CB012D9182D408CED7B884F441D4D5FE353@nambxv01a.corp.adobe.com>
Content-Language: en-GB-hixie
Content-Style-Type: text/css
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
X-Mailman-Approved-At: Sat, 23 Jan 2010 09:37:59 -0800
Cc: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Jan 2010 06:32:24 -0000

On Fri, 22 Jan 2010, Larry Masinter wrote:
> >>
> >> A message with more than one content-type header should be treated as 
> >> malformed.
> > 
> > What does it mean to treat the response as malformed?  I've seen 
> > examples of servers that blissfully send more than one Content-Type 
> > header.  This document just describes how to process the responses 
> > without making a judge about whether the server is acting properly or 
> > not.
> 
> Implementations should be allowed to not do sniffing when the 
> content-type is malformed, even when they do sniffing when the 
> content-type is missing, or specific kinds of sniffing when the 
> content-type is supplied but just wrong.

I strongly disagree. Getting reliably interoperable behaviour in all user 
agents trumps theoretical concerns about what is right or wrong, IMHO.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'

v2.23.0 | Report a Bug | By Email