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

[Helmut Hummel]

Hi Steffen,

thanks for your proposal. In general it looks good to me.

However some nitpicks:

1. Like already mentioned by Masi, I would replace urlScheme with
url_scheme, but also in locallang.
2. Use elseif like Georg suggested
3. I would like to see class constants to check aginst, instead of
numbers. What about adding SCHEME_HTTP and SCHEME_HTTPS ot
t3lib_utility_http. Probably we find a place where we could add even
more (all) schemes as constants.

Regards Helmut

On 01.09.10 17:59, Steffen Ritter wrote:
> 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