[TYPO3-core] RFC #15621: Feature: TYPO3 misses page-option to force SSL oder Non-SSL to page

[Steffen Ritter]

Am 01.09.2010 17:59, schrieb Steffen Ritter:
> Hey list,
> This is an SVN patch request.
>
> Type: Feature
>
> Bugtracker references:
> http://bugs.typo3.org/view.php?id=15621
>
> Branches:
> trunk
>
> Problem:
> TYPO3 misses the possibility to "enforce" one page to be ssl or to be no
> ssl.
> In rfc 11950 we introduced the possibility into typolink to set an
> scheme (http / https) to the rendered link url.
>
> Solution:
> Since the typolink function generally is enabled to that since 0011950,
> we easily can integrate such functionality to core.
>
> Notes:
> The patch consists of 3 parts:
> - adding the selector to the page tca/sql/locallang
> - adding 3 lines to typolink to check if this value is set
> - adding a redirect to TSFE if a force is set and called by another
> request type
>
> regards
> Steffen
Hey list,
here is my v3 taking all your comments into account.

regards

Steffen
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: addHTTPSEnforcement_v3.diff
URL: <http://lists.typo3.org/pipermail/typo3-team-core/attachments/20100908/f00448c9/attachment.txt>