Solves the bug described in #2656. Instead of returning a 400 in case of a missing content type, it now returns a 415. For further details, see the issue.
It does not add the return of an Accept header in case of a mismatched content type. But I would not see this as a bug but rather as an enhancement which needs its own issue.
Additional context:
Has already been merged into master in the PR #2657. This PR is for 4.x.
Motivation:
Solves the bug described in #2656. Instead of returning a 400 in case of a missing content type, it now returns a 415. For further details, see the issue.
It does not add the return of an
Accept
header in case of a mismatched content type. But I would not see this as a bug but rather as an enhancement which needs its own issue.Additional context:
Has already been merged into
master
in the PR #2657. This PR is for4.x
.