Added support into the v2 API to fix an issue (6433) where if there is a semicolon and fields after it the API would return an "invalid Content-type" message even if the content type was actually correct