EXT: HTTP/HTTPS Switch¶

What does it do?¶

This extension lets you decide if your TYPO3 pages should be displayed with an HTTPS or HTTP scheme. The extension is compatible with RealURL, and can be used as well for a single page or for complete site sections.

This extension does the same job as the extension "HTTPS Enforcer / macmade.net" (https_macmade) but is built with Extbase and Fluid. The extension depends on TYPO3 6.1.

Screenshots¶

Here you see what the extension does:

Installation¶

The installation of this extension is very simple. Just connect to the Typo3 Extension Repository and download «HTTP/HTTPS Switch» (ax_https).

You'll then need to include the static TS template in your main TS template, like in the picture below:

You will also need to call the HTTPS Switch plugin in the page object of your main template, like this:

page = PAGE
page.5 < lib.tx_axhttps
page.10 = FLUIDTEMPLATE

Note that you do not have to use FluidTemplate. The extension is also compatible with TemplaVoila and the old templating system.

For CSS stylesheets and other links, you must also set "config.baseURL" conditionally this way:

[page|tx_axhttps_protocol = 1][globalVar = LIT:1 = {$plugin.tx_axhttps.settings.mode}]
  config.baseURL = https://www.mydomain.net/
[else]
  config.baseURL = http://www.mydomain.net/
[global]

Once it's done, you'll be able to configure the default behavior. This is done through the TS constant editor. You can do that on your main template, or in extension templates, if you want a different behavior for a site section, for instance.

Then, if you edit the headers of a page, you'll notice a new field. This will configure the HTTP scheme for that single page:

Now let's take a look at some configurations.

If you've enforced your website with an HTTPS scheme, every page will be displayed under HTTPS unless they are configured to use HTTP.

If you don't set the enforce mode globally, the settings from each page will be taken. But in that case, if you visit an HTTPS enforced page, and then a page that is not enforced, neither HTTPS or HTTP, you'll stay with an HTTPS scheme.

In that way, you should be able to achieve the most complex configurations for your website.

0.2.0¶

0.1.0¶