Extension Manager configuration¶
Go to the Extension Manager, find the extension pagenotfoundhandling and click on the extension name to open the configuration interface.
The available options are structured in four groups:
Basic options¶
Property
default404Page
Data type
int
Description
An uid of a page out of the page tree that will be displayed as content of the 404 page. ‘0’ disables this feature. See section Available markers for details on marker substitution
Default
0
Property
defaultTemplateFile
Data type
string
Description
This template will be used if no default404Page
is configured.
See section Available markers for details on marker
substitution
Default
EXT:pagenotfoundhandling/Resources/Private/Templates/default.html
Property
additional404GetParams
Data type
string
Description
These will be appended to the URL when fetching default404Page
.
The marker ###CURRENT_URL###
is replaced within this string.
Default
Property
default403Page
Data type
int
Description
Behaves like default404Page
, but activates a separate handling for
requests on protected pages. Leave empty to disable this feature.
Default
Property
default403TemplateFile
Data type
string
Description
Behaves like defaultTemplateFile
, but activates a separate handling
for requests on protected pages. Leave empty to disable this feature.
Default
Property
additional403GetParams
Data type
string
Description
These will be appended to the URL when fetching
default404Page
/default403Page
in case of access restriction
error. The marker ###CURRENT_URL###
is replaced within this string.
Default
Advanced options¶
Property
absoluteReferencePrefix
Data type
string
Description
If your TYPO3 installation runs in a subdir of the DOCUMENT_ROOT, add the relative path from DOCUMENT_ROOT to the installation here
Default
Property
disableDomainConfig
Data type
boolean
Description
Domain dependent configurations will be ignored. The TCA of sys_domain will not be extended.
Default
0
Property
preserveFeuserLogin
Data type
boolean
Description
Preserve a frontend user login session by sending the session cookie when fetching the 404/403 page.
This option internally enables the option sendXForwardedForHeader
when a valid login session is detected.
To get this working, you need to configure your TYPO3 installation in one of the following ways.
1: Configure the IP address of the machine, where TYPO3 runs on as
reverseProxyIP
:
$GLOBALS['TYPO3_CONF_VARS']['SYS']['reverseProxyIP'] = '127.0.0.1';
$GLOBALS['TYPO3_CONF_VARS']['SYS']['reverseProxyHeaderMultiValue'] = 'first';
2: Alternatively you can disable the lockIP
for frontend login
sessions:
CAUTION: this decreases the security of the frontend login sessions and is NOT RECOMMENDED, especially for public websites! Use only if you know what you do.
$GLOBALS['TYPO3_CONF_VARS']['FE']['lockIP'] = 0;
Default
0
Language options¶
Property
languageParam
Data type
string
Description
The GET variable that holds the language uid. In most cases this will be “L”, which is the TYPO3 default.
Default
L
Property
ignoreLanguage
Data type
boolean
Description
The language parameter in the request URL ($_GET['L']
) will be
ignored, default language will be used. See also option
defaultLanguageKey
.
Default
0
Property
defaultLanguageKey
Data type
boolean
Description
This tells the extension which language is your default language.
You can use values like ‘de’ for german, ‘dk’ for danish, etc..
Use this only if your default language is not english (TYPO3 default).
At the moment the extension only supports german and english, to use
your own language, see the option locallangFile
below.
Default
default
Property
forceLanguage
Data type
int
Description
This language is one from sys_language (the pid is shown in the
selector box). So, if you have no language records in your setup,
the selector box will be empty. If this option is used $_GET['L']
will be ignored.
Default
Property
locallangFile
Data type
string
Description
This language xml file will be included and used for marker substitution. See section Available markers for details.
Default
HTTP options¶
Property
passthroughContentTypeHeader
Data type
boolean
Description
When a 404 page is defined, the HTTP header Content-Type
will be
captured and sent when delivering the 404 page
Default
0
Property
sendXForwardedForHeader
Data type
boolean
Description
Send the REMOTE_ADDR
in the X-Forwarded-For
HTTP header when
fetching the 404 page.
Be sure to configure
$GLOBALS['TYPO3_CONF_VARS']['SYS']['reverseProxyIP']
correctly
when using this feature.
Default
0
Property
additionalHeaders
Data type
string
Description
Send additional HTTP headers with the 404/403 page response. Multiple headers are separated with ‘|’
Default
Property
digestAuthentication
Data type
string
Description
If the 404/403 page is access restricted with HTTP digest authentication, you can configure the username and password here.
Format: username:password
(colon-separated username and password)
HTTP digest authentication requires cURL to be installed and enabled in
$GLOBALS['TYPO3_CONF_VARS']['SYS']['curlUse']
Note: this is NOT required for HTTP basic authentication (this type of authentication works out-of-the box)!
Default