Bug #55618

Wrong HTTP status code for missing entities

Added by Bastian Waidelich over 7 years ago. Updated about 7 years ago.

Status:
Resolved
Priority:
Should have
Category:
Error
Target version:
-
Start date:
2014-02-03
Due date:
% Done:

100%

Estimated time:
PHP Version:
Has patch:
No
Complexity:

Description

When an exception is thrown in PropertyMapper::convert() it is always wrapped in a \TYPO3\Flow\Property\Exception leading to the default exception handling which sets the status code of the HTTP response to 500.
At least in the case of a TargetNotFoundException this should be a 404 status instead

#1

Updated by Bastian Waidelich over 7 years ago

  • Subject changed from Wrong HTTP status code for removed entities to Wrong HTTP status code for missing entities
#2

Updated by Gerrit Code Review over 7 years ago

  • Status changed from Accepted to Under Review

Patch set 1 for branch master of project Packages/TYPO3.Flow has been pushed to the review server.
It is available at https://review.typo3.org/27298

#3

Updated by Bastian Waidelich about 7 years ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100

Also available in: Atom PDF