Content-type could use its own verifier

[macosforgebot]

douglm@… originally submitted this as ticket:387

---

Tests fail because the content-type header value doesn't match but is actually valid, e.g. g test for

text/calendar;charset=utf-8

and receive

text/calendar; charset=UTF-8

The space(s) after the semi-colon are valid as is the UC "UTF-8"

This might be complicated enough to justify its own verifier

[macosforgebot]

@wsanchez originally submitted this as comment:1:⁠ticket:387

• Radar deleted
• Priority changed from 5: Not set to 2: Expected

[macosforgebot]

@wsanchez originally submitted this as comment:2:⁠ticket:387

• Milestone set to Later