Actions
Bug #18485
closedeID_include should generate 404 error if the extension cannot be included
Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2008-03-20
Due date:
% Done:
0%
Estimated time:
TYPO3 Version:
4.1
PHP Version:
5.2
Tags:
Complexity:
Is Regression:
No
Sprint Focus:
Description
if any invalid eID request is sent to index_ts.php, typo3 sends a 200 OK header anyway, although it does not require/include anything and exits.
in this case, a 404 header would be appropriate to indicate that it didn't work out.
(issue imported from #M7912)
Files
Updated by Alexander Opitz over 11 years ago
- Category deleted (
Communication) - Status changed from New to Needs Feedback
- Target version deleted (
0)
The issue is very old, does this issue exists in newer versions of TYPO3 CMS (4.5 or 6.1)?
Updated by Alexander Opitz about 11 years ago
- Status changed from Needs Feedback to Closed
- Is Regression set to No
No feedback for over 90 days.
Actions