Comment 8 for bug 194642

It may also be prudent to reiterate that the changes made remain compliant with MIME Part One, RFC 2045, §5, ¶ 3, which states:

"The Content-Type header field specifies the nature of the data in the body of an entity by giving media type and subtype identifiers, and by providing auxiliary information that may be required for certain media types. After the media type and subtype names, the remainder of the header field is simply a set of parameters, specified in an attribute=value notation. The ordering of parameters is not significant."

Since the only change is the ordering to work around nasty parsers in existing software that breaks this portion of the standard, there _should_ be no additional side effects. To date, I have observed none.