Issue #2971012 by Wim Leers, borisson_: ContentTypeHeaderMatcher should not run for DELETE requests
parent
aeb5733c8a
commit
246a31c42f
|
@ -15,10 +15,10 @@ class ContentTypeHeaderMatcher implements FilterInterface {
|
|||
* {@inheritdoc}
|
||||
*/
|
||||
public function filter(RouteCollection $collection, Request $request) {
|
||||
// The Content-type header does not make sense on GET requests, because GET
|
||||
// requests do not carry any content. Nothing to filter in this case. Same
|
||||
// for all other safe methods.
|
||||
if ($request->isMethodSafe(FALSE)) {
|
||||
// The Content-type header does not make sense on GET or DELETE requests,
|
||||
// because they do not carry any content. Nothing to filter in this case.
|
||||
// Same for all other safe methods.
|
||||
if ($request->isMethodSafe(FALSE) || $request->isMethod('DELETE')) {
|
||||
return $collection;
|
||||
}
|
||||
|
||||
|
|
|
@ -61,6 +61,7 @@ class ContentTypeHeaderMatcherTest extends UnitTestCase {
|
|||
['HEAD'],
|
||||
['OPTIONS'],
|
||||
['TRACE'],
|
||||
['DELETE'],
|
||||
];
|
||||
}
|
||||
|
||||
|
|
Loading…
Reference in New Issue