#2934152: ContentTypeHeaderMatcher should not run for GET, HEAD, OPTIONS or TRACE requests improved ContentTypeHeaderMatcher's logic. It's a correct bugfix. But over at #2934149-19: [>=8.5] JSON API routes not specifying _content_type_format route requirement, resulting in bad DX we just noticed that there is another bug/oversight: DELETE requests. DELETE requests never have a request body. And so it doesn't make sense to require a Content-Type request header either.
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | 2971012-6.patch | 1.68 KB | wim leers |
Comments
Comment #2
wim leersFailing test.
Comment #3
wim leersAnd the fix.
Comment #5
borisson_This has test-coverage and looks to be really simple. I'm not to sure about the documentation. I think it'd be better do do something like this:
However, It's just a suggestion.
Comment #6
wim leers#5: I knew that comment was off! Thanks 🙏
Fixed!
P.S.: thank you very much for the review! How did you find this issue so fast!? 😲
Comment #7
borisson_That looks better!
I had some time and was looking at the needs review queue to see if I could help with any of the open issues.
Comment #8
wim leers<3
Comment #9
alexpottCommitted and pushed 246a31c42f to 8.6.x and e3004ccad6 to 8.5.x. Thanks!
Comment #12
wim leers:O
This was one of my fastest core commits EVER. Thank you so much @alexpott!
Comment #13
wim leersAnd bam, #2934149-25: [>=8.5] JSON API routes not specifying _content_type_format route requirement, resulting in bad DX is now passing the tests that previously were failing! ❤️