Bug #24945
closed
Status "500 Internal Server Error" returned, if page is not found
Added by Steffen Gebert over 13 years ago.
Updated almost 13 years ago.
Description
Due to the ExceptionHandler, no status 404 is returned, if a page is not found, but status 500 instead.
This happens with and without URL (only the message differs)
(issue imported from #M17471)
Files
Sorry, have no time to work on this. I think we could use the t3lib_message_ErrorMessagePage and output the message, instead of throwing the Exception (which results in the Exception Handler sending the 500).
Attached the patches out of Gerrit.
I've tested 17471_v2-4.5.diff with TYPO3 4.5.2 and the error still persists.
In the frontend, I get the error 500.
The log has the following entry:
Core: Exception handler (WEB): Uncaught TYPO3 Exception: The page did not exist or was inaccessible. Reason: The requested page does not exist! | RuntimeException thrown in file /html/typo3_src-4.5.2/typo3/sysext/cms/tslib/class.tslib_fe.php in line 1476
Okay, this line was not covered, as I was unsure. I'm currently investigating and will provide an updated patch soon.
Attached an updated patch.
Time to get into Git, Peter ;-)
Patch set 6 of change Ia6c7686c720863aa80e390c452527cabb338bde3 has been pushed to the review server.
It is available at http://review.typo3.org/1245
- Status changed from New to Resolved
- % Done changed from 0 to 100
- Category deleted (
Communication)
- Target version changed from 4.5.1 to 4.5.3
Thanks.. I also noticed this last week and fixed it for master in some places (hower not in 4-5, of course).
Continued in #25727
What exactly do you mean with "not in 4-5"?
I noticed the problem and fixed it partly in master, but forgot to conclude that this also require a patch for 4-5 branch. So everything safe, as soon as #25727 is in.
- Status changed from Resolved to Closed
Also available in: Atom
PDF