Allowing other content types for json

[sbdchd]

looking through the code,

dropshot/dropshot/src/handler.rs

Lines 1018 to 1026 in 5063b8d

	(expected, requested) => {
	return Err(HttpError::for_bad_request(
	None,
	format!(
	"expected content type \"{}\", got \"{}\"",
	expected.mime_type(),
	requested.mime_type()
	),
	))

, I think currently content types for json besides application/json aren't supported

my use case is I'm trying reimplement an AWS api where the client uses a application/x-amz-json-1.0 header for json so being able to have a route take a custom json content type would be useful

edit: as a work around I think I could skip parsing the body as json, but then I'd lose the fancy open api stuff

[ahl]

Thanks for filing the issue. Would the parsing of content with application/x-amz-json-1.0 be identical to that of application/json? Perhaps we can provide an interface that allows one to specify aliases for application/json.

[sbdchd]

honestly not entirely sure, but in my use case I would assume they're the same

rel: https://stackoverflow.com/questions/65118844/what-is-application-x-amz-json-and-how-is-it-different-from-application-json