Re: Ticket 260: multiple disposition types, was: Comments on draft-ietf-httpbis-content-disp

On Tue, Nov 2, 2010 at 1:43 AM, Julian Reschke <> wrote:
>> Note that it may be resolved by indicating that 'treat as invalid' is
>> specific to the application at hand. As such, I'd like initial discussion of
>> this in the WG to focus on:
>>  a) use cases: how different implementations / applications may want to
>> have different notions of 'invalid' (or not), and
>>  b) security: what the security impact of having different notions of
>> 'invalid' here may be, and
>>  c) interoperability: likewise, the interop impact.
>>> This section does not define how user agents ought to process header
>>> field values with multiple disposition types.  According to this test
>>> case<>, user agents
>>> MUST use the first disposition type.
>> Ticket:
> That's incorrect.
> Have a look at <>; in this
> case IE picks the second one.
> There is no interop here today, and this doesn't seem to be a problem in
> practice.

That's a pretty defeatist attitude.  Put another way, four out of five
browsers agree: we ought to use the first disposition type.


Received on Tuesday, 2 November 2010 08:56:34 UTC