Re: Media-type containing semi-colon but no parameter

On 2011-07-04 15:49, Anne van Kesteren wrote:
> Currently per HTTP the following constitutes an incorrect Content-Type
> header:
>
> Content-Type: text/html;
>
> as per media-type the semi-colon must be followed by a parameter. No
> implementation I know of treats that as an unknown media type however.
> They arrive at the somewhat obvious text/html media type. It would make
> sense to me if HTTP were changed to allow a trailing semi-colon.

Well, this may break existing implementations that enforce it.

Have you seen header field instances like this in the wild?

Best regards, Julian