Force Redirect HTTP to HTTPS

Falco · 2월 15, 2017, 12:45오전

Add the SSL-only cookies among other things.

In our recommended way to setting SSL, this is all handled automatically:

templates/web.ssl.template.yml

master


      
          - exec:
             cmd:
               - "mkdir -p /shared/ssl/"
          - replace:
             filename: "/etc/nginx/conf.d/discourse.conf"
             from: /server.+{/
             to: |
               server {
                 listen 80;
                 return 301 https://$$ENV_DISCOURSE_HOSTNAME$request_uri;
               }
               server {
          - replace:
             filename: "/etc/nginx/conf.d/discourse.conf"
             from: /listen 80;\s+gzip on;/m
             to: |
               listen 443 ssl http2;
               SSL_TEMPLATE_SSL_BLOCK
          - replace:
             filename: "/etc/nginx/conf.d/discourse.conf"
             from: /listen 80;\s+listen \[::\]:80;\s+gzip on;/m

글		댓글	조회수
How do I configure Discourse behind an AWS or Google Cloud Proxy with SSL Self-hosting	20	3606	3월 25, 2019
Website does not forward to https Self-hosting	11	1007	3월 12, 2020
DiscourseConnect generates HTTP redirects even with force_https on Self-hosting discourseconnect	4	402	5월 27, 2024
X-Forwarded-For proxy tag not recognized by Discourse? Self-hosting	9	3148	1월 19, 2018
Installing discourse with http only (no https) Self-hosting	1	1448	5월 9, 2021

Force Redirect HTTP to HTTPS

Related topics