readBody() does not take into account application/x-www-form-urlencoded; charset=utf-8

[efraimbart]

If charset=utf-8 is added to the content type readBody() will attempt to parse the body as json and fail. See

h3/src/utils/body.ts

Lines 107 to 115 in d11f817

	if (contentType === "application/json") {
	parsed = _parseJSON(body, options.strict ?? true) as T;
	} else if (contentType === "application/x-www-form-urlencoded") {
	parsed = _parseURLEncodedBody(body!) as T;
	} else if (contentType.startsWith("text/")) {
	parsed = body as T;
	} else {
	parsed = _parseJSON(body, options.strict ?? false) as T;
	}

.

[Hebilicious]

I think we should support charset in the content type header by either extracting it first or using string.contains

[pi0]

Thanks for reporting issue. It will be resolved in next release by (4af66eb). I have added an internal comment that in next iterations, we might actually use the charset to handle encoding.