Opened 9 years ago

Closed 9 years ago

#260 closed design (wontfix)

Multiple Disposition types

Reported by: mnot@… Owned by:
Priority: normal Milestone: unassigned
Component: content-disp Severity: In WG Last Call
Keywords: Cc:

Description

​http://tools.ietf.org/html/draft-ietf-httpbis-content-disp-03#section-3.2

This section does not define how user agents ought to process header field values with multiple disposition types. According to this test case <​http://greenbytes.de/tech/tc2231/#attandinline2>, user agents MUST use the first disposition type.

Change History (2)

comment:1 Changed 9 years ago by julian.reschke@…

The argument is flawed. <​http://greenbytes.de/tech/tc2231/#attandinline> demonstrates that IE picks the type by name, not by position.

There is no interoperability here today, and there's no evidence yet that it is needed. After all, the header is invalid.

Proposal: close as WONTFIX.

comment:2 Changed 9 years ago by julian.reschke@…

  • Resolution set to wontfix
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.