[TYPO3-dev] bug 10502 - IPmaskList - shows just white page instead of BE-Login
Daniel Bruessler
danielb at typo3.org
Fri Feb 20 12:38:08 CET 2009
Hello Steffen and Martin,
I would like it best when just the BE debug() output is blocked with
this, because that is what a developer would like to hide when searching
for a problem in a BE-extension.
I see in t3lib/config_default.php that there is already the check for
devIPmask. So the setting "devIPmask" could be used JUST for FE-errors
and the setting "['BE']['IPmaskList']" just for BE-errors.
function debug($variable='', $name='*variable*', $line='*line*',
$file='*file*', $recursiveDepth=3, $debugLevel=E_DEBUG) {
// If you wish to use the debug()-function, and it does not output
something, please edit the IP mask in TYPO3_CONF_VARS
if (!t3lib_div::cmpIP(t3lib_div::getIndpEnv('REMOTE_ADDR'),
$GLOBALS['TYPO3_CONF_VARS']['SYS']['devIPmask'])) return;
I just don't know how to check if TYPO3 is in FE-mode or in BE-mode in
the moment.
Cheers!
Daniel
> Steffen Kamper schrieb:
>> Hi Daniel,
>>
>> i can confirm this.
>>
>> The problem occurs in init.php where this condition is true all the time:
>>
>> if (trim($TYPO3_CONF_VARS['BE']['IPmaskList']) &&
>> !(defined('TYPO3_cliMode') && TYPO3_cliMode))
>
> But I think this is ok. A misconfigured security measure should result
> in a denied access.
>
> Of course a blank screen is never helpful. TYPO3 should send the
> appropriate HTTP header for "access denied" and log the configuration error.
>
> Masi
More information about the TYPO3-dev
mailing list