On Mon, May 6, 2013 at 4:33 PM, Julian Aubourg <j...@ubourg.net> wrote: > It seems strange the spec would require a case-sensitive value for > Content-Type in certain circumstances. Are these deviations from the > case-insensitiveness of the header really necessary ? Are they beneficial > for authors ? It seems to me they promote bad practice (case-sensitive > testing of Content-Type).
There's only two things that seem to work well over a long period of time given multiple implementations and developers coding toward the dominant implementation (this describes the web). 1. Require the same from everyone. 2. Require randomness. Anything else is likely to lead some subset of developers to depend on certain things they really should not depend on and will force everyone to match the conventions of what they depend on (if you're in bad luck you'll get mutual exclusive dependencies; the web has those too). E.g. the ordering of the members of the <canvas> element is one such thing (trivial bad luck example is User-Agent). -- http://annevankesteren.nl/
