[TYPO3-core] RFC #5442: Feature: HTTPS port number in lockSSL redirect should be configurable
Christopher Hlubek
hlubek at networkteam.com
Mon Feb 18 14:05:11 CET 2008
This is an SVN patch request.
Type: New feature
Bugtracker references:
http://bugs.typo3.org/view.php?id=5442
Branches:
trunk
Problem:
Securing backend access for multiple TYPO3 webs with SSL in virtual
hosting environments with limited ip addresses is only possible using
different HTTPS ports. But the lockSSL option itself does only a
redirect from http://{$url} to https://{$url} , which doesn't allow to
change to a custom HTTPS port on redirect.
Solution:
A new configuration option $TYPO3_CONF_VARS['BE']['lockSSLPort'] that
adds the HTTPS port to the url used for redirect with lockSSL.
Notes:
Documentation for the configuration setting is inlined in
't3lib/config_default.php' and
'typo3/sysext/install/modules/setup/conf.php' respectively (not yet in
the patch attached to the bugtracker).
-Christopher Hlubek
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: TYPO3-lockSSLPort-3.patch
Url: http://lists.netfielders.de/pipermail/typo3-team-core/attachments/20080218/1733de0e/attachment-0001.txt
More information about the TYPO3-team-core
mailing list