Feature #86844

Allow 404-handling for non-defined page-types (typeNum)

Added by Stefan Neufeind 15 days ago. Updated 9 days ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
Frontend
Target version:
-
Start date:
2018-11-03
Due date:
% Done:

0%

PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

You might previously have used pages with a typeNum different than 0, like a print-type or some type used for fetching JSON-data. Once that page-type is no longer defined calling those URLs leads to errors. But it doesn't trigger 404-handling (like showing a page-not-found information).

History

#1 Updated by Holger Drosdek 9 days ago

Maybe corresponding to the allowed languages: config.linkVars = L(0-1).

I noticed at some sites multiple log records like this one testing SQL-Injection:

Core: Exception handler (WEB): Uncaught TYPO3 Exception: #1294587217: The page is not configured! [type=11111111111111][]. This means that there is no TypoScript object of type PAGE with typeNum=11111111111111 configured. | TYPO3\CMS\Core\Error\Http\ServiceUnavailableException thrown in file /var/www/virtual/domain.de/typo3_src-8.7.19/typo3/sysext/frontend/Classes/Controller/TypoScriptFrontendController.php in line 2491. Requested URL: https://www.domain.de/themen/thema1/?ps=en%252525252527A%25252525253D0%2527A%253D0&type=11111111111111" UNION SELECT CHAR,CHAR,CHAR,CHAR,CHAR,CHAR,CHAR,CHAR,CHAR,CHAR,CHAR,CHAR,CHAR,CHAR,CHAR,CHAR,CHAR,CHAR,CHAR,CHAR,CHAR,CHAR,CHAR,CHAR,CHAR%20--%20/*%20order%20by%20%22as%20/*

Also available in: Atom PDF