Content-type check breaks when additional directives are supplied

[kimburgess]

The current Content-Type header check performs an exact match for the media-type only. If the charset directive is supplied this results in an incorrect HTTP 406 response. Same is true for the `boundary directive (if supported).