I added this to the milestone because it's a bug we introduced in master recently.

I don't think this bug was in 1.9.0 unless we do indeed want to check for json in 1.9.

I remember the pr which introduced this check

@cpuguy83 you're right, this is not in 1.9.

LGTM, thanks @calavera

Need to bump the API version in the version check.

oh cr*p you're right #etoomanyversions

fixed, thanks!

Sorry, one more thing... Test for pre 1.22 behavior?
Also seems like there probably isn't any test ensuring json is The only content-type supported here going forward either.

I added a test to check that we keep backwards compatibility.

Also seems like there probably isn't any test ensuring json

@cpuguy83 it looks like we had already a test sending "application/json" content types to the start endpoint. It didn't fail before because the didn't check the content type, and it didn't fail when we forced it with CheckJSON because it was the expected content type.

All in all, this ensures we keep backwards compatibility and adds a test to verify it. We already have a test that checks the current valid behavior.

LGTM