92
edits
Setting Up Wildcard Subdomains with SSL on a Debian Application: Difference between revisions
Jump to navigation
Jump to search
Setting Up Wildcard Subdomains with SSL on a Debian Application (view source)
Revision as of 05:53, 31 October 2024
, 31 October 2024no edit summary
mNo edit summary |
No edit summary |
||
| Line 199: | Line 199: | ||
location / { | location / { | ||
proxy_pass http://< | proxy_pass http://<APP_UPSTREAM>/; | ||
proxy_set_header Host \$host; | proxy_set_header Host \$host; | ||
proxy_set_header X-Forwarded-For \$proxy_add_x_forwarded_for; | proxy_set_header X-Forwarded-For \$proxy_add_x_forwarded_for; | ||
| Line 231: | Line 231: | ||
nginx -q -t && service nginx reload | nginx -q -t && service nginx reload | ||
</pre> | </pre> | ||
In the case of our guide with the kaboom-api example, <code><APP_UPSTREAM></code> is <code>kaboom-api</code>, it refers to the backend application server(s) receiving proxied requests. | |||
==== e. Wrapping everything in an if statement ==== | ==== e. Wrapping everything in an if statement ==== | ||