- From: Anne van Kesteren <annevk@opera.com>
- Date: Sat, 22 Oct 2011 17:11:32 +0900
On Sat, 22 Oct 2011 17:09:21 +0900, Daniel Glazman <daniel.glazman at disruptive-innovations.com> wrote: > Le 21/10/11 22:19, Adam Barth a ?crit : >> Thanks. Fixed. > > Speaking of that document, I notice section 4 forces the presence of a > whitespace after the semi-colon preceeding the parameter, eg: > > text/plain; charset=iso-8859-1 > > This is wrong. Nothing in the MIME or the HTTP specs says such a > whitespace is mandatory. Whitespace is explicitely forbidden between > type and subtype, between parameter-name and parameter-value, but that's > all. AFAIC, |text/plain;charset=iso-8859-1| is perfectly valid and > |text/plain ; charset=iso-8859-1| is perfectly valid too. We do not want to sniff text/plain more than strictly necessary. -- Anne van Kesteren http://annevankesteren.nl/
Received on Saturday, 22 October 2011 01:11:32 UTC