TR-4678 Update sample NGINX configuration file

content/docs/tech-resources/using-proxy-https-tracking-domain.md

@@ -1,5 +1,5 @@
 ---
-lastUpdated: "05/03/2023"
+lastUpdated: "09/29/2023"
 title: "Using a Reverse Proxy for HTTPS Tracking Domain"
 description: "SparkPost supports HTTPS engagement tracking for customers via self-service for all SparkPost customers. To enable SSL engagement tracking for a domain, additional configuration for SSL keys is required.  This resource outlines the use of a reverse proxy to host SSL certificates"
 ---
@@ -65,12 +65,11 @@ server { # simple reverse-proxy
    listen       80;
    server_name  click.nddurant.com;
 
-   proxy_set_header Host $host;
-
    # pass requests for dynamic content to rails/turbogears/zope, et al
    location / {
      set $backend "spgo.io";
      proxy_pass https://$backend;
+     proxy_set_header Host $host;
    }
 }
 ```
@@ -228,8 +227,6 @@ server { # simple reverse-proxy
     ssl_certificate      /etc/letsencrypt/live/click.nddurant.com/fullchain.pem; # managed by Certbot
     ssl_certificate_key  /etc/letsencrypt/live/click.nddurant.com/privkey.pem; # managed by Certbot
 
-    proxy_set_header Host $host;
-
     # Security improvements
     ssl_protocols TLSv1.2;
     ssl_prefer_server_ciphers on;
@@ -239,6 +236,7 @@ server { # simple reverse-proxy
     location / {
         set $backend "spgo.io";
         proxy_pass https://$backend;
+        proxy_set_header Host $host;
         proxy_set_header X-Forwarded-For $remote_addr; # pass the client IP to the open & click tracker
         server_tokens off; # suppress NGINX giving version/OS information on error pages
     }