Task #87302
closed
Throw better exception if a page for 404 error handling throws an fluid exception
0%
Description
Problem/Description¶
Reproduce the following scenario¶
- Using the new site configuration and setting a 404 page like
t3://page?uid=15 - force a fluid exception on a CE in the target 404 page (e.g. f:for VH on a string)
- open
https://yourproject.localdevdomain/foobarmuhbar42 - This leads to the following exception:
#1544172838 RuntimeException Error handler could not fetch error page "https://yourproject.localdevdomain/404", reason: Client error: `GET https://yourproject.localdevdomain/404` resulted in a `404 The requested page does not exist` response
A dev/integrator may be confused. Feels like any environment specific problem.
ToDo(s)¶
- If possible – show a better exception to the TYPO3 Integrator
Updated by Martin Kutschker over 5 years ago
I suggest that in production context the handler falls back to the standard typo3 error layout if the HTTP status is not 200 or an empty string. The reason for the fallback should be logged.
Updated by Susanne Moog over 4 years ago
- Status changed from New to Needs Feedback
I cannot reproduce the issue. In production context with your example, the fluid error is suppressed and the user doesn't get to see it.
In Development context I do not get the same message you do, but instead:
Error handler could not fetch error page "https://core.dev.site/404.html", reason: Server error: `GET https://core.dev.site/404.html` resulted in a `500 Internal Server Error` response: <!DOCTYPE html> <html> <head> <meta charset="UTF-8" /> <title>TYPO3 Exception</title> <meta (truncated...)
which is correct as the 404.html is a 500 internal server - with the logging and messages that throws, which should be clear enough for a dev. What would you expect here?
Updated by Benni Mack almost 3 years ago
- Status changed from Needs Feedback to Rejected
Closing due to lack of feedback, if you feel this is still an issue, let me know and I will re-open the issue.