#51378Show a more helpful message if [BE][lockSSL] = 1 and no https is available
Description
During a site upgrade from 4.5 to 6.2, an OTAP configuration was auto-migrated to a LocalConfiguration.php file. This went mostly well, except for the fact that the O (or Development context) does not have SSL enabled.
The BE-lockSSL setting was however set to 1 in the LocalConfiguration.php.
Accessing the TYPO3 backend produced a very unhelpful 404 message.
It took me some time to trace it to the lockSSL.
A more helpful error message would be nice instead of this security by obscurity 404 message.