Can we get https enabled for UAT?

[pgwillia]

I’ve sometimes run across instances where a “thing” works in http but fails under https

Originally posted by @pgwillia in #1680 (comment)

[pgwillia]

# config/nginx.conf
server {

  listen 80 ssl;

  client_max_body_size 4G;
  keepalive_timeout 10;

  ssl_certificate     library.ualberta.ca.bundle.crt;
  ssl_certificate_key library.ualberta.ca.key;
  ssl_protocols       TLSv1 TLSv1.1 TLSv1.2;
  ssl_ciphers         HIGH:!aNULL:!MD5;

  error_page 500 502 504 /500.html;
  error_page 497  301 =307 https://$host:$server_port$request_uri;
...
}

# docker-compose.yml
nginx:
    restart: always
    image: nginx
    depends_on:
      - web
    env_file: .env_deployment
    volumes:
      - ./config/nginx.conf:/etc/nginx/conf.d/default.conf
      - ../UALcert/library.ualberta.ca.key:/etc/nginx/library.ualberta.ca.key
      - ../UALcert/library.ualberta.ca.crt:/etc/nginx/library.ualberta.ca.bundle.crt
      - assets:/app/public/
    ports:
      - "80:80"

[pgwillia]

need to set these headers

upstream myapp {
  server              unix:///path/to/puma.sock;
}
...
location / {
  proxy_pass        http://myapp;
  proxy_set_header  Host $host;
  proxy_set_header  X-Forwarded-For $proxy_add_x_forwarded_for;
  proxy_set_header  X-Forwarded-Proto $scheme;
  proxy_set_header  X-Forwarded-Ssl on; # Optional
  proxy_set_header  X-Forwarded-Port $server_port;
  proxy_set_header  X-Forwarded-Host $host;
}