Ergebnis 1 bis 11 von 11

Thema: HTTPS on Contao 4.4

  1. #1
    Contao-Nutzer
    Registriert seit
    06.12.2017.
    Beiträge
    24

    Standard HTTPS on Contao 4.4

    Hello,

    How to put the HTTPS on contao 4.4
    SSL is enabled in my host.

    The site is accessible in HTTP and HTTPS, automatic redirection to HTTPS does not.

    An idea?

    Thank you in advance.

  2. #2
    Community-Moderator
    Wandelndes Contao-Lexikon
    Avatar von Spooky
    Registriert seit
    12.04.2012.
    Ort
    Scotland
    Beiträge
    34.109
    Partner-ID
    10107

    Standard

    You need to provide more information about what your problem is and what you want to achieve.

    Do you want an automatic redirect to HTTPS? If yes - this is not something that is done within Contao. You need to do that within your Webserver's configuration (e.g. via the .htaccess, if you use Apache).

  3. #3
    Contao-Nutzer
    Registriert seit
    06.12.2017.
    Beiträge
    24

    Standard

    See below what I realize
    Geändert von HypNoTeeZz (06.12.2017 um 15:49 Uhr)

  4. #4
    Contao-Nutzer
    Registriert seit
    06.12.2017.
    Beiträge
    24

    Standard

    Excuse me this is not the right htaccess.

    Here's what I really do:

    <IfModule mod_headers.c>
    # Allow access from all domains for webfonts (see contao/core-bundle#528)
    <FilesMatch "\.(ttf|ttc|otf|eot|woff2?|font\.css)$">
    Header set Access-Control-Allow-Origin "*"
    </FilesMatch>
    </IfModule>

    <IfModule mod_rewrite.c>
    RewriteEngine On

    # Determine the RewriteBase automatically and set it as environment variable.
    # If you are using Apache aliases to do mass virtual hosting or installed the
    # project in a subdirectory, the base path will be prepended to allow proper
    # resolution of the app.php file and to redirect to the correct URI. It will
    # work in environments without path prefix as well, providing a safe, one-size
    # fits all solution. But as you do not need it in this case, you can comment
    # the following 2 lines to eliminate the overhead.
    RewriteCond %{REQUEST_URI}::$1 ^(/.+)/(.*)::\2$
    RewriteRule ^(.*) - [E=BASE:%1]

    # Sets the HTTP_AUTHORIZATION header removed by Apache
    RewriteCond %{HTTP:Authorization} .
    RewriteRule ^ - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]

    # Redirect to URI without front controller to prevent duplicate content
    # (with and without `/app.php`). Only do this redirect on the initial
    # rewrite by Apache and not on subsequent cycles. Otherwise we would get an
    # endless redirect loop (request -> rewrite to front controller ->
    # redirect -> request -> ...).
    # So in case you get a "too many redirects" error or you always get redirected
    # to the start page because your Apache does not expose the REDIRECT_STATUS
    # environment variable, you have 2 choices:
    # - disable this feature by commenting the following 2 lines or
    # - use Apache >= 2.3.9 and replace all L flags by END flags and remove the
    # following RewriteCond (best solution)
    RewriteCond %{ENV:REDIRECT_STATUS} ^$
    RewriteRule ^app\.php(?:/(.*)|$) %{ENV:BASE}/$1 [R=301,L]

    # If the requested filename exists, simply serve it.
    # We only want to let Apache serve files and not directories.
    RewriteCond %{REQUEST_FILENAME} -f
    RewriteRule ^ - [L]

    # Rewrite all other queries to the front controller.
    RewriteRule ^ %{ENV:BASE}/app.php [L]
    </IfModule>

    <IfModule !mod_rewrite.c>
    <IfModule mod_alias.c>
    # When mod_rewrite is not available, we instruct a temporary redirect of
    # the start page to the front controller explicitly so that the website
    # and the generated links can still be used.
    RedirectMatch 302 ^/$ /app.php/
    # RedirectTemp cannot be used instead
    </IfModule>
    </IfModule>

    RewriteEngine On
    RewriteCond %{HTTPS} off
    RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} [R,L]

  5. #5
    Contao-Urgestein Avatar von folkfreund
    Registriert seit
    09.04.2010.
    Beiträge
    1.928

    Standard

    You should place the rule inside the <IfModule mod_rewrite.c>.

    The working rule differ a bit depending on server settings.
    This is what works for me (Contao 4.4.7) - just the mod_rewrite part:
    Code:
    <IfModule mod_rewrite.c>
        RewriteEngine On
    
    
        # Determine the RewriteBase automatically and set it as environment variable.
        # If you are using Apache aliases to do mass virtual hosting or installed the
        # project in a subdirectory, the base path will be prepended to allow proper
        # resolution of the app.php file and to redirect to the correct URI. It will
        # work in environments without path prefix as well, providing a safe, one-size
        # fits all solution. But as you do not need it in this case, you can comment
        # the following 2 lines to eliminate the overhead.
        RewriteCond %{REQUEST_URI}::$1 ^(/.+)/(.*)::\2$
        RewriteRule ^(.*) - [E=BASE:%1]
    
    
        RewriteCond %{HTTP_HOST} ^www\.MYDOMAIN\.de [NC]
        RewriteRule (.*) https://MYDOMAIN.de/$1 [R=301,L]
    
    
        # Sets the HTTP_AUTHORIZATION header removed by Apache
        RewriteCond %{HTTP:Authorization} .
        RewriteRule ^ - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
    
    
        # Redirect to URI without front controller to prevent duplicate content
        # (with and without `/app.php`). Only do this redirect on the initial
        # rewrite by Apache and not on subsequent cycles. Otherwise we would get an
        # endless redirect loop (request -> rewrite to front controller ->
        # redirect -> request -> ...).
        # So in case you get a "too many redirects" error or you always get redirected
        # to the start page because your Apache does not expose the REDIRECT_STATUS
        # environment variable, you have 2 choices:
        # - disable this feature by commenting the following 2 lines or
        # - use Apache >= 2.3.9 and replace all L flags by END flags and remove the
        #   following RewriteCond (best solution)
        RewriteCond %{ENV:REDIRECT_STATUS} ^$
        RewriteRule ^app\.php(?:/(.*)|$) %{ENV:BASE}/$1 [R=301,L]
    
    
        # If the requested filename exists, simply serve it.
        # We only want to let Apache serve files and not directories.
        RewriteCond %{REQUEST_FILENAME} -f
        RewriteRule ^ - [L]
    
    
        RewriteCond %{HTTPS} !=on
        RewriteCond %{ENV:HTTPS} !=on
        RewriteRule .* https://%{SERVER_NAME}%{REQUEST_URI} [R=301,L]
    
    
        # Rewrite all other queries to the front controller.
        RewriteRule ^ %{ENV:BASE}/app.php [L]
    </IfModule>
    Note: this is a redirect to MYDOMAIN.de (without www) - see the 2 lines quite at the beginning!

  6. #6
    Contao-Nutzer
    Registriert seit
    06.12.2017.
    Beiträge
    24

    Standard

    PHP-Code:
    <IfModule mod_headers.c>
        
    # Allow access from all domains for webfonts (see contao/core-bundle#528)
        
    <FilesMatch "\.(ttf|ttc|otf|eot|woff2?|font\.css)$">
            
    Header set Access-Control-Allow-Origin "*"
        
    </FilesMatch>
    </
    IfModule>

    <
    IfModule mod_rewrite.c>
        
    RewriteEngine On

        
    # Determine the RewriteBase automatically and set it as environment variable.
        # If you are using Apache aliases to do mass virtual hosting or installed the
        # project in a subdirectory, the base path will be prepended to allow proper
        # resolution of the app.php file and to redirect to the correct URI. It will
        # work in environments without path prefix as well, providing a safe, one-size
        # fits all solution. But as you do not need it in this case, you can comment
        # the following 2 lines to eliminate the overhead.
        
    RewriteCond %{REQUEST_URI}::$^(/.+)/(.*)::\2$
        
    RewriteRule ^(.*) - [E=BASE:%1]

        
    # Sets the HTTP_AUTHORIZATION header removed by Apache
        
    RewriteCond %{HTTP:Authorization} .
        
    RewriteRule ^ - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]

        
    # Redirect to URI without front controller to prevent duplicate content
        # (with and without `/app.php`). Only do this redirect on the initial
        # rewrite by Apache and not on subsequent cycles. Otherwise we would get an
        # endless redirect loop (request -> rewrite to front controller ->
        # redirect -> request -> ...).
        # So in case you get a "too many redirects" error or you always get redirected
        # to the start page because your Apache does not expose the REDIRECT_STATUS
        # environment variable, you have 2 choices:
        # - disable this feature by commenting the following 2 lines or
        # - use Apache >= 2.3.9 and replace all L flags by END flags and remove the
        #   following RewriteCond (best solution)
        
    RewriteCond %{ENV:REDIRECT_STATUS} ^$
        
    RewriteRule ^app\.php(?:/(.*)|$) %{ENV:BASE}/$[R=301,L]

        
    # If the requested filename exists, simply serve it.
        # We only want to let Apache serve files and not directories.
        
    RewriteCond %{REQUEST_FILENAME} -f
        RewriteRule 
    ^ - [L]

        
    # Rewrite all other queries to the front controller.
        
    RewriteRule ^ %{ENV:BASE}/app.php [L]
    </
    IfModule>

    <
    IfModule mod_rewrite.c>
        
    RewriteEngine On


        
    # Determine the RewriteBase automatically and set it as environment variable.
        # If you are using Apache aliases to do mass virtual hosting or installed the
        # project in a subdirectory, the base path will be prepended to allow proper
        # resolution of the app.php file and to redirect to the correct URI. It will
        # work in environments without path prefix as well, providing a safe, one-size
        # fits all solution. But as you do not need it in this case, you can comment
        # the following 2 lines to eliminate the overhead.
        
    RewriteCond %{REQUEST_URI}::$^(/.+)/(.*)::\2$
        
    RewriteRule ^(.*) - [E=BASE:%1]


        
    RewriteCond %{HTTP_HOST} ^www\.handi-defis\.fr [NC]
        
    RewriteRule (.*) https://handi-defis.fr/$1 [R=301,L]


        # Sets the HTTP_AUTHORIZATION header removed by Apache
        
    RewriteCond %{HTTP:Authorization} .
        
    RewriteRule ^ - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]


        
    # Redirect to URI without front controller to prevent duplicate content
        # (with and without `/app.php`). Only do this redirect on the initial
        # rewrite by Apache and not on subsequent cycles. Otherwise we would get an
        # endless redirect loop (request -> rewrite to front controller ->
        # redirect -> request -> ...).
        # So in case you get a "too many redirects" error or you always get redirected
        # to the start page because your Apache does not expose the REDIRECT_STATUS
        # environment variable, you have 2 choices:
        # - disable this feature by commenting the following 2 lines or
        # - use Apache >= 2.3.9 and replace all L flags by END flags and remove the
        #   following RewriteCond (best solution)
        
    RewriteCond %{ENV:REDIRECT_STATUS} ^$
        
    RewriteRule ^app\.php(?:/(.*)|$) %{ENV:BASE}/$[R=301,L]


        
    # If the requested filename exists, simply serve it.
        # We only want to let Apache serve files and not directories.
        
    RewriteCond %{REQUEST_FILENAME} -f
        RewriteRule 
    ^ - [L]


        
    RewriteCond %{HTTPS} !=on
        RewriteCond 
    %{ENV:HTTPS} !=on
        RewriteRule 
    .* https://%{SERVER_NAME}%{REQUEST_URI} [R=301,L]


        # Rewrite all other queries to the front controller.
        
    RewriteRule ^ %{ENV:BASE}/app.php [L]
    </
    IfModule
    I put your code in my .htaccess file but it does not matter

  7. #7
    Contao-Nutzer
    Registriert seit
    06.12.2017.
    Beiträge
    24

  8. #8
    Contao-Nutzer
    Registriert seit
    06.12.2017.
    Beiträge
    24

    Standard

    Oops! Error on my part, everything works fine,
    Thank you for your help.

  9. #9
    Community-Moderator
    Wandelndes Contao-Lexikon
    Avatar von Spooky
    Registriert seit
    12.04.2012.
    Ort
    Scotland
    Beiträge
    34.109
    Partner-ID
    10107

    Standard

    You misunderstood the directions. Restore the original .htaccess. You should insert your HTTPS related rewrite rules after this line.

    // ah ok

  10. #10
    Contao-Nutzer
    Registriert seit
    06.12.2017.
    Beiträge
    24

    Standard

    Neues Problem.
    Auf einer neuen Site übergebe ich https auch, außer dass es meine CSS-Dateien nicht berücksichtigt. In der fe_page bleibt die Basis in http
    Eine Idee?

  11. #11
    Community-Moderator
    Wandelndes Contao-Lexikon
    Avatar von Spooky
    Registriert seit
    12.04.2012.
    Ort
    Scotland
    Beiträge
    34.109
    Partner-ID
    10107

    Standard

    Evt. verwendest du bei der neuen Seite einen SSL Proxy? Siehe zB https://github.com/contao/core-bundle/issues/895

Aktive Benutzer

Aktive Benutzer

Aktive Benutzer in diesem Thema: 1 (Registrierte Benutzer: 0, Gäste: 1)

Lesezeichen

Lesezeichen

Berechtigungen

  • Neue Themen erstellen: Nein
  • Themen beantworten: Nein
  • Anhänge hochladen: Nein
  • Beiträge bearbeiten: Nein
  •