[TYPO3-core] RFC #15621: Feature: TYPO3 misses page-option to force SSL oder Non-SSL to page
Xavier Perseguers
typo3 at perseguers.ch
Wed Oct 13 10:18:10 CEST 2010
Hi,
Steffen Ritter wrote:
> Am 13.10.2010 10:00, schrieb Steffen Kamper:
>> We have to warn also. So as Marcus mentioned it will be problematic if a
>> reverse ssl proxy is installed and configured. Also the server has to
>> have
>> SSL abilities.
> If someone has such a configuration in place we may be able to respect
> this settings, too. But as long at there is noone, i'm not able to do so.
I did not read the whole thread but I could make some tests of such an
environment if needed. It would be great to support this correctly:
browser <-- https --> ssl-proxy <-- http --> webserver
As this is seldomly supported by applications (as they do not "see" the
https and as such don't want to create such links blindly), I did this:
browser <-- https --> ssl-proxy <-- https --> webserver
with a dumb certificate on the second segment that my ssl-proxy does not
check at all. This way the applications are OK to generate SSL links.
Xavier
More information about the TYPO3-team-core
mailing list